public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
* Speeding up development of test-container testcases
@ 2024-04-23 18:15 Joseph Simmons-Talbott
  2024-04-23 18:56 ` Florian Weimer
  0 siblings, 1 reply; 3+ messages in thread
From: Joseph Simmons-Talbott @ 2024-04-23 18:15 UTC (permalink / raw)
  To: libc-help

Hi,

I'm working on developing some test-container testcases and am
currently using the workflow where I run configure and then make to
build glibc.  I am having to run a full 'make check' in order to be
able to run a test-container testcase individually with 'make test
t=...'.  I've attempted to determine the part of 'make check' that I
need to build before I can successfully just run a single testcase
after a clean build of glibc but have been unsuccessful so far.  Any
tips are greatly appreciated.

The error I get is: error: test-container.c:832: Cannot create testroot lock.

Perhaps I'm doing something wrong or expecting behavior that I shouldn't.

Thanks,
Joe


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Speeding up development of test-container testcases
  2024-04-23 18:15 Speeding up development of test-container testcases Joseph Simmons-Talbott
@ 2024-04-23 18:56 ` Florian Weimer
  2024-04-23 20:25   ` Joseph Simmons-Talbott
  0 siblings, 1 reply; 3+ messages in thread
From: Florian Weimer @ 2024-04-23 18:56 UTC (permalink / raw)
  To: Joseph Simmons-Talbott via Libc-help; +Cc: Joseph Simmons-Talbott

* Joseph Simmons-Talbott via Libc-help:

> I'm working on developing some test-container testcases and am
> currently using the workflow where I run configure and then make to
> build glibc.  I am having to run a full 'make check' in order to be
> able to run a test-container testcase individually with 'make test
> t=...'.  I've attempted to determine the part of 'make check' that I
> need to build before I can successfully just run a single testcase
> after a clean build of glibc but have been unsuccessful so far.  Any
> tips are greatly appreciated.

Looking at my shell history, I believe these commands can be used to
recreate the testroot with the current glibc build:

  rm `pwd`/testroot.pristine/install.stamp
  make -j`nproc` `pwd`/testroot.pristine/install.stamp

Thanks,
Florian


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Speeding up development of test-container testcases
  2024-04-23 18:56 ` Florian Weimer
@ 2024-04-23 20:25   ` Joseph Simmons-Talbott
  0 siblings, 0 replies; 3+ messages in thread
From: Joseph Simmons-Talbott @ 2024-04-23 20:25 UTC (permalink / raw)
  To: Florian Weimer; +Cc: Joseph Simmons-Talbott via Libc-help

On Tue, Apr 23, 2024 at 2:56 PM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Joseph Simmons-Talbott via Libc-help:
>
> > I'm working on developing some test-container testcases and am
> > currently using the workflow where I run configure and then make to
> > build glibc.  I am having to run a full 'make check' in order to be
> > able to run a test-container testcase individually with 'make test
> > t=...'.  I've attempted to determine the part of 'make check' that I
> > need to build before I can successfully just run a single testcase
> > after a clean build of glibc but have been unsuccessful so far.  Any
> > tips are greatly appreciated.
>
> Looking at my shell history, I believe these commands can be used to
> recreate the testroot with the current glibc build:
>
>   rm `pwd`/testroot.pristine/install.stamp
>   make -j`nproc` `pwd`/testroot.pristine/install.stamp

That worked.  Thank you so much.

Thanks,
Joe


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-04-23 20:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-23 18:15 Speeding up development of test-container testcases Joseph Simmons-Talbott
2024-04-23 18:56 ` Florian Weimer
2024-04-23 20:25   ` Joseph Simmons-Talbott

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).