From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Sadineni Harish <sadineniharish8446@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Inquiry for gcc test results
Date: Wed, 24 Jan 2024 09:18:09 +0000 [thread overview]
Message-ID: <CAH6eHdR_=YVjQsOJm9NZCuZ8OL2BMJfg61osZA83YJWL-ZWA6Q@mail.gmail.com> (raw)
In-Reply-To: <CAK4mW0AnAekdWL-Nz3fqkJQCfmY+UVufNYVw2Lw4F7bg8Nmf5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On Wed, 24 Jan 2024, 07:59 Sadineni Harish via Gcc-help, <
gcc-help@gcc.gnu.org> wrote:
> Hi all,
>
> I was not able to find all the test results for gcc from following link
> https://gcc.gnu.org/pipermail/gcc-testresults/2024-January/805339.html,
> only fail tests , xpass tests and summary information were available.
>
Yes, the script that summarises the test results only shows the tests that
give the wrong result. That's how it's supposed to work, because there are
tens of thousands of tests and nearly all of them work correctly.
If the email summary included all the passing tests then the email would be
too large and get rejected from the mailing list.
> Where can I find all the test results like tests for expected passes,
> expected failures and unsupported tests and also where to find failure
> logs.
>
You can't find those online, but we I said, everything now shown there
passed, or failed as expected (XFAIL), or tests something for a different
target (UNSUPPORTED).
If you want the full results you need to run the tests yourself.
> Your assistance is highly valuable, and I look forward to your response
>
> Thanks and Regards
> Harish Sadineni
>
next prev parent reply other threads:[~2024-01-24 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 7:57 Sadineni Harish
2024-01-24 9:18 ` Jonathan Wakely [this message]
2024-01-24 9:19 ` Jonathan Wakely
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='CAH6eHdR_=YVjQsOJm9NZCuZ8OL2BMJfg61osZA83YJWL-ZWA6Q@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sadineniharish8446@gmail.com \
/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).