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: Thu, 23 Feb 2023 14:54:51 +0000	[thread overview]
Message-ID: <bug-30157-131-eSyPHVFzhF@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 #5 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> ---
To give more details about which tests were run: in the "make check" output,
about "ifunc-":

env GCONV_PATH=/home/vlefevre/software/glibc-build/iconvdata
LOCPATH=/home/vlefevre/software/glibc-build/localedata LC_ALL=C  
/home/vlefevre/software/glibc-build/elf/tst-ifunc-isa-1-static  >
/home/vlefevre/software/glibc-build/elf/tst-ifunc-isa-1-static.out; \
../scripts/evaluate-test.sh elf/tst-ifunc-isa-1-static $? true false >
/home/vlefevre/software/glibc-build/elf/tst-ifunc-isa-1-static.test-result

and

env GCONV_PATH=/home/vlefevre/software/glibc-build/iconvdata
LOCPATH=/home/vlefevre/software/glibc-build/localedata LC_ALL=C
GLIBC_TUNABLES=glibc.cpu.hwcaps=-SSE4_2,-AVX,-AVX2,-AVX512F 
/home/vlefevre/software/glibc-build/elf/tst-ifunc-isa-2-static  >
/home/vlefevre/software/glibc-build/elf/tst-ifunc-isa-2-static.out; \
../scripts/evaluate-test.sh elf/tst-ifunc-isa-2-static $? true false >
/home/vlefevre/software/glibc-build/elf/tst-ifunc-isa-2-static.test-result

so that one can see that tst-ifunc-isa-1-static.out and
tst-ifunc-isa-2-static.out files are rebuilt as the corresponding tests are
run. But there is nothing for the tst-ifunc-fault-bindnow and
tst-ifunc-fault-lazy tests.

And near the end, one has:

../scripts/merge-test-results.sh -s /home/vlefevre/software/glibc-build/elf/
elf \
  [...] tst-gnu2-tls1 tst-ifunc-fault-bindnow tst-ifunc-fault-lazy
tst-ifunc-isa-1 tst-ifunc-isa-1-static tst-ifunc-isa-2 tst-ifunc-isa-2-static
tst-ifunc-textrel tst-initfinilazyfail [...]

Here, tst-ifunc-fault-bindnow and tst-ifunc-fault-lazy are included in the
merged results. So the results from an old "make check" are used.

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

  parent reply	other threads:[~2023-02-23 14:54 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 [this message]
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

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