public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug build/25836] New: Test container not properly created when running single test
@ 2020-04-16 14:20 msc at linux dot ibm.com
  2020-04-16 14:34 ` [Bug build/25836] " carlos at redhat dot com
  2022-06-05  3:55 ` sam at gentoo dot org
  0 siblings, 2 replies; 3+ messages in thread
From: msc at linux dot ibm.com @ 2020-04-16 14:20 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25836

            Bug ID: 25836
           Summary: Test container not properly created when running
                    single test
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: msc at linux dot ibm.com
                CC: carlos at redhat dot com
  Target Milestone: ---

I recently noticed that trying to run a single containerized test using `make
test t=<...>` fails if run before `make check`.

For example, right after building glibc:
$ make test t=stdlib/tst-system
[...]
FAIL: stdlib/tst-system
original exit status 1
error: test-container.c:766: Cannot create testroot lock.

I've tried this with many tests that use containers and the results are always
the same.

Apparently this happens because testroot.* directories are not properly created
in such cases:
~/build/glibc$ ls testroot.pristine
ls: cannot access 'testroot.pristine': No such file or directory
~/build/glibc$ ls testroot.root
ls: cannot access 'testroot.root': No such file or directory

The rule to create testroot.pristine is in the top-level Makefile:
$(tests-container) $(addsuffix /tests,$(subdirs)) : \
                $(objpfx)testroot.pristine/install.stamp

However `tests-container` is only defined by each subdir Makefile, so this rule
is never triggered for individual tests, as `tests-container` is always empty
in
this context.

Tested with commit c580e6466d6da8262820cdbad19f32c5546226cf.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

* [Bug build/25836] Test container not properly created when running single test
  2020-04-16 14:20 [Bug build/25836] New: Test container not properly created when running single test msc at linux dot ibm.com
@ 2020-04-16 14:34 ` carlos at redhat dot com
  2022-06-05  3:55 ` sam at gentoo dot org
  1 sibling, 0 replies; 3+ messages in thread
From: carlos at redhat dot com @ 2020-04-16 14:34 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25836

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2020-04-16
     Ever confirmed|0                           |1

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
This is just a limitation of the implementation of the helper targets.

You could probably detect the container rootfs is missing and generate it, and
then use the stamp to never do that again.

Note: We are still unable to dynamically update the rootfs when the
implementation changes, so that will not be resolved.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

* [Bug build/25836] Test container not properly created when running single test
  2020-04-16 14:20 [Bug build/25836] New: Test container not properly created when running single test msc at linux dot ibm.com
  2020-04-16 14:34 ` [Bug build/25836] " carlos at redhat dot com
@ 2022-06-05  3:55 ` sam at gentoo dot org
  1 sibling, 0 replies; 3+ messages in thread
From: sam at gentoo dot org @ 2022-06-05  3:55 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25836

Sam James <sam at gentoo dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sam at gentoo dot org

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

end of thread, other threads:[~2022-06-05  3:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-16 14:20 [Bug build/25836] New: Test container not properly created when running single test msc at linux dot ibm.com
2020-04-16 14:34 ` [Bug build/25836] " carlos at redhat dot com
2022-06-05  3:55 ` sam at gentoo dot org

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).