From: Jeff Law <jeffreyalaw@gmail.com>
To: Alexandre Oliva <oliva@gnu.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] compare_tests: distinguish c-c++-common results by tool
Date: Wed, 20 Dec 2023 10:17:08 -0700 [thread overview]
Message-ID: <1cd3fee7-2a0c-4e33-91c2-4559286adeb9@gmail.com> (raw)
In-Reply-To: <or8r5p2xmp.fsf@lxoliva.fsfla.org>
On 12/19/23 23:31, Alexandre Oliva wrote:
> On Dec 20, 2023, Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>> So the strub tests in c-c++-common are problematical. They get run
>> twice, once for C, once for C++. Yet the name of the test is the same
>> in both runs. (by the name, I mean the name emitted into the dejagnu
>> summary and log files).
>
>> Thus if you have a test in there which passes in one context, but
>> fails in the other, comparison tools like contrib/compare_tests may
>> erroneously report the tests as both a test which now fails, but
>> passed before and a test which now passes but failed before.
>
>> It looks like some of the strub tests are currently known to fail with
>> C++ and are triggering this problem
>
> Yeah, type warnings/errors are different between C and C++, and this is
> noticeable with permissible conversions between strub types.
>
>
>> A third option would be to change the compare_tests tool to somehow
>> distinguish between the C and C++ tests. Not sure how feasible that
>> is.
>
> Most feasible among the possibilities ;-)
>
> I've tested the following by comparing my obj-x86_64-linux-gnu test tree
> with itself. Ok to install?
>
>
> When compare_tests compares both C and C++ tests in c-c++-common, they
> get the same identifier, so expected differences in results across
> languages become undesirably noisy.
>
> This patch adds tool identifiers to tests, so that runs by different
> tools are not confused by the compare logic.
>
> It also fixes a bug in reporting differences, that would attempt to
> print an undefined fname (the definitions are in subshell loops), and
> adjusts the target insertion to match tabs in addition to blanks after
> colons.
>
>
> for contrib/ChangeLog
>
> * compare_tests: Add tool to test lines. Match tabs besides
> blanks to insert tool and target. Don't print undefined fname
Go for it. It's hard to know if there'll be fallout in the consumers,
but I think if there is pain, it should be short term.
Jeff
next prev parent reply other threads:[~2023-12-20 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 4:40 Problems with strub tests Jeff Law
2023-12-20 6:31 ` [PATCH] compare_tests: distinguish c-c++-common results by tool Alexandre Oliva
2023-12-20 17:17 ` Jeff Law [this message]
2024-01-07 1:51 ` Problems with strub tests Hans-Peter Nilsson
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=1cd3fee7-2a0c-4e33-91c2-4559286adeb9@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=oliva@gnu.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).