public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/30157] parallel "make check" randomly skips tests
Date: Sat, 25 Feb 2023 20:47:57 +0000	[thread overview]
Message-ID: <bug-30157-131-ZaikGCESqM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30157-131@http.sourceware.org/bugzilla/>

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

--- Comment #12 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
(In reply to Carlos O'Donell from comment #11)
> (In reply to Vincent Lefèvre from comment #10)
> > I've done another "make check". So now there are tests whose last execution
> > is
> > * 2023-02-24 (today)
> > * 2023-02-23
> > * 2023-02-22 around 17:43
> > * 2023-02-22 around 17:12 (corresponding to the first "make check")
> > 
> > (No source files have been changed after the initial checkout.)
> 
> Just to be clear, while you say "No source files have been changed", what is
> actually important is *dependencies*.
> 
> In the case of tst-audit23 we have the following:
> 
> 2283 $(objpfx)tst-audit23.out: $(objpfx)tst-auditmod23.so \
> 2284                           $(objpfx)tst-audit23mod.so

The timestamps of these files:

-rwxr-xr-x 1 20080 2023-02-22 17:12:15 elf/tst-audit23mod.so*
-rwxr-xr-x 1 24632 2023-02-22 17:12:15 elf/tst-auditmod23.so*

(The timestamps of the elf/tst*.so files go from 2023-02-22 17:12:14 to
2023-02-22 17:12:23.)

So they still correspond to the first "make check".

> The tests need their output file (the *.out file) and this says that output
> needs the two audit modules compiled, so they get built before the test is
> built and run.
> 
> I would be curious to know if the *.out file was changed, or the *.so files
> were changed, since they are are of the set of dependencies for the test.

For the elf/*.out files:

cventin:...tware/glibc-build> ls -lgot **/elf/tst*.out
-rw-r--r-- 1     75 2023-02-23 15:32:36 elf/tst-glibc-hwcaps-cache.out
-rw-r--r-- 1     68 2023-02-23 15:32:36 elf/tst-glibc-hwcaps-2-cache.out
[...]
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-debug1.out
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-audit25a.out
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-audit25b.out
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-audit23.out
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-audit24a.out
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-audit24b.out
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-audit24c.out
-rw-r--r-- 1      0 2023-02-23 15:32:36 elf/tst-audit24d.out
-rw-r--r-- 1      9 2023-02-23 15:32:36 elf/tst-audit11.out
[...]
-rw-r--r-- 1      0 2023-02-23 15:32:35 elf/tst-dst-static.out
-rw-r--r-- 1     48 2023-02-22 17:12:25 elf/tst-dso-ordering9.out
-rw-r--r-- 1     48 2023-02-22 17:12:24 elf/tst-dso-ordering3.out
[...]
-rw-r--r-- 1      0 2023-02-22 17:12:18 elf/tst-relro-ldso.out
-rw-r--r-- 1      0 2023-02-22 17:12:14 elf/tst-glibcelf.out
-rw-r--r-- 1 160643 2023-02-22 17:12:12 elf/tst-ldconfig-p.out
-rw-r--r-- 1      0 2023-02-22 17:12:12 elf/tst-ldconfig-X.out

Since the tst*.out files were generated after their dependencies (built around
2023-02-22 17:12 in the first "make check"), I would have expected them not to
be rebuilt on 2023-02-23 (assuming that's how the glibc test rules work).

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

      parent reply	other threads:[~2023-02-25 20:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 13:35 [Bug build/30157] New: " vincent-srcware at vinc17 dot net
2023-02-23 13:39 ` [Bug build/30157] " vincent-srcware at vinc17 dot net
2023-02-23 13:43 ` vincent-srcware at vinc17 dot net
2023-02-23 14:03 ` sam at gentoo dot org
2023-02-23 14:10 ` schwab@linux-m68k.org
2023-02-23 14:15 ` vincent-srcware at vinc17 dot net
2023-02-23 14:54 ` vincent-srcware at vinc17 dot net
2023-02-23 16:18 ` schwab@linux-m68k.org
2023-02-23 17:38 ` vincent-srcware at vinc17 dot net
2023-02-23 19:05 ` carlos at redhat dot com
2023-02-24  9:02 ` vincent-srcware at vinc17 dot net
2023-02-24  9:22 ` vincent-srcware at vinc17 dot net
2023-02-25 19:04 ` carlos at redhat dot com
2023-02-25 20:47 ` vincent-srcware at vinc17 dot net [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-30157-131-ZaikGCESqM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).