From: Joseph Myers <joseph@codesourcery.com>
To: <alexandra.khirnova@gmail.com>
Cc: libc-alpha@sourceware.org, "Mark Wielaard" <mark@klomp.org>,
"Alexandra Hájková" <ahajkova@redhat.com>
Subject: Re: [PATCH] Add valgrind smoke test
Date: Mon, 24 Jan 2022 18:34:28 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2201241831300.377985@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CACfmkTpQhYyB3ZZjL3kqxvBm7Y6uxmw_frO_vn_9wc-_mhSdJg@mail.gmail.com>
I'm seeing
FAIL: elf/tst-valgrind-smoke
for the x86_64 configurations when running build-many-glibcs.py (and
UNSUPPORTED for other architectures). No execution tests of the newly
built glibc should be run at all unless
ifeq ($(run-built-tests),yes)
but I don't see any such conditional around the
tests-special += $(objpfx)tst-valgrind-smoke.out
that causes this test to be run.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-01-24 18:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 14:40 Alexandra Hájková
2021-12-07 11:56 ` Mark Wielaard
2021-12-07 20:32 ` DJ Delorie
2021-12-07 20:58 ` Florian Weimer
2021-12-07 21:10 ` DJ Delorie
2021-12-10 12:56 ` Mark Wielaard
2021-12-10 13:07 ` Florian Weimer
2021-12-10 19:15 ` DJ Delorie
2021-12-13 12:55 ` Mark Wielaard
2021-12-17 18:26 ` Alexandra Hájková
2021-12-17 21:07 ` DJ Delorie
2021-12-20 11:31 ` Alexandra Petlanova Hajkova
2021-12-20 11:37 ` Alexandra Hájková
2022-01-10 12:13 ` Mark Wielaard
2022-01-10 12:38 ` Adhemerval Zanella
2022-01-12 17:15 ` Alexandra Hájková
2022-01-20 19:35 ` Alexandra Hájková
2022-01-24 18:34 ` Joseph Myers [this message]
2022-01-26 17:46 ` Joseph Myers
2022-01-26 17:59 ` Mark Wielaard
2022-01-26 18:40 ` Joseph Myers
2022-01-26 19:23 ` Mark Wielaard
2022-01-20 21:29 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2021-05-24 12:15 Alexandra Hájková
2021-05-24 14:28 ` Carlos O'Donell
2021-05-24 19:28 ` Joseph Myers
2021-06-28 8:29 ` Florian Weimer
2021-06-28 18:33 ` Joseph Myers
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=alpine.DEB.2.22.394.2201241831300.377985@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=ahajkova@redhat.com \
--cc=alexandra.khirnova@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.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).