From: Philip Herron <philip.herron@embecosm.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: Test results for gccrs on Debian unstable aarch64
Date: Thu, 3 Jun 2021 12:58:46 +0100 [thread overview]
Message-ID: <CAB2u+n0mEv8=yqra7WbwS9JFfUpYnxfrgQHN=ZHWcwLCvX5Ymg@mail.gmail.com> (raw)
In-Reply-To: <d06fcc54-2fa7-5eca-3eb4-2af59a0631a2@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
I just had a thought it would be nice if we could keep a matrix of
different platforms gccrs has been tested on, and they could have states of:
1. Build Failure
2. Test Failures link to log
3. Tests pass, no unexpected results
What if we maintained a section in the wiki for this?
Thanks,
--Phil
On Thu, 3 Jun 2021 at 12:28, John Paul Adrian Glaubitz <
glaubitz@physik.fu-berlin.de> wrote:
> Hi!
>
> Just built revision 324dfb828cec09f7638b48b6e25e4007b45b9cbc on Debian
> unstable aarch64.
>
> Testsuite passes without any issues, attaching the full log.
>
> Adrian
>
> === rust tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for
> target.
> Using /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ...
> Running
> /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ...
> Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ...
> Running
> /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ...
>
> === rust Summary ===
>
> # of expected passes 2368
> # of expected failures 26
> make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc'
> make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc'
>
> --
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer - glaubitz@debian.org
> `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
> --
> Gcc-rust mailing list
> Gcc-rust@gcc.gnu.org
> https://gcc.gnu.org/mailman/listinfo/gcc-rust
>
[-- Attachment #2: Type: text/html, Size: 2693 bytes --]
next prev parent reply other threads:[~2021-06-03 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 11:28 John Paul Adrian Glaubitz
2021-06-03 11:58 ` Philip Herron [this message]
2021-06-03 12:05 ` John Paul Adrian Glaubitz
2021-06-03 12:10 ` Philip Herron
2021-06-03 19:05 ` Mark Wielaard
2021-06-03 22:16 ` Mark Wielaard
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='CAB2u+n0mEv8=yqra7WbwS9JFfUpYnxfrgQHN=ZHWcwLCvX5Ymg@mail.gmail.com' \
--to=philip.herron@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.de \
/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).