public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrew Dean via gcc" <gcc@gcc.gnu.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: How to properly build and run testsuite?
Date: Thu, 21 Nov 2019 22:21:00 -0000	[thread overview]
Message-ID: <SN2PR00MB0125667A7188FFE4EA647DFCEA4E0@SN2PR00MB0125.namprd00.prod.outlook.com> (raw)
In-Reply-To: <CAH6eHdR-GzNv0wngJAwt063ZKa3Vd-aTajieOU7gGeO6hB3++w@mail.gmail.com>

> > > > Whereas the most recent reported results (10.0.0 20191118) show
> > > > only 2
> > > unexpected failures and no unexpected successes in the gcc summary.
> > >
> > > Which results are you looking at?
> > > Two failures sounds very low, it's probably not running the guality
> > > tests which usually fail.
> > >
> > I searched the mailing list for x86_64-pc-linux-gnu to make sure I was
> > comparing apples to apples, and this was the most recent report:
> > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.
> > gnu.org%2Fml%2Fgcc-testresults%2F2019-
> 11%2Fmsg01190.html&amp;data=02%7
> >
> C01%7CAndrew.Dean%40microsoft.com%7Cb89abb6ea9f34a0916d908d76ed0
> 3783%7
> >
> C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637099712871926073
> &amp;sda
> >
> ta=KooYFswCjKMaV%2FQ3D6tc03WAej8MfQ4Zl9H9kjtR%2B6Y%3D&amp;rese
> rved=0
> 
> Yes, I thought you might be looking at that one. That has:
> # of unsupported tests 7126
> which seems high. Here's a more typical set of results:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.gnu
> .org%2Fml%2Fgcc-testresults%2F2019-
> 11%2Fmsg01255.html&amp;data=02%7C01%7CAndrew.Dean%40microsoft.co
> m%7Cb89abb6ea9f34a0916d908d76ed03783%7C72f988bf86f141af91ab2d7c
> d011db47%7C1%7C0%7C637099712871926073&amp;sdata=ujcoGkSL45wodz
> A50F7NvlyHPGzt8MKnTQbUzye3JIw%3D&amp;reserved=0
> 
> The one you looked at is built on an EC2 instance, so might be missing
> something (GDB?) needed for the guality tests.
> 
> So I don't think you're doing anything wrong, you just got unlucky and looked at
> one which skips most of the tests that are failing for you.

Thanks for your help!

      reply	other threads:[~2019-11-21 22:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 19:10 Andrew Dean via gcc
2019-11-21 21:15 ` Jonathan Wakely
2019-11-21 21:30   ` Andrew Dean via gcc
2019-11-21 22:14     ` Jonathan Wakely
2019-11-21 22:21       ` Andrew Dean via gcc [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=SN2PR00MB0125667A7188FFE4EA647DFCEA4E0@SN2PR00MB0125.namprd00.prod.outlook.com \
    --to=gcc@gcc.gnu.org \
    --cc=Andrew.Dean@microsoft.com \
    --cc=jwakely.gcc@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).