public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
* Test results for gccrs on Debian unstable aarch64
@ 2021-06-03 11:28 John Paul Adrian Glaubitz
  2021-06-03 11:58 ` Philip Herron
  0 siblings, 1 reply; 6+ messages in thread
From: John Paul Adrian Glaubitz @ 2021-06-03 11:28 UTC (permalink / raw)
  To: gcc-rust

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

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

[-- Attachment #2: rust-aarch64.log.gz --]
[-- Type: application/gzip, Size: 55921 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Test results for gccrs on Debian unstable aarch64
  2021-06-03 11:28 Test results for gccrs on Debian unstable aarch64 John Paul Adrian Glaubitz
@ 2021-06-03 11:58 ` Philip Herron
  2021-06-03 12:05   ` John Paul Adrian Glaubitz
  2021-06-03 19:05   ` Mark Wielaard
  0 siblings, 2 replies; 6+ messages in thread
From: Philip Herron @ 2021-06-03 11:58 UTC (permalink / raw)
  To: John Paul Adrian Glaubitz; +Cc: gcc-rust

[-- 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 --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Test results for gccrs on Debian unstable aarch64
  2021-06-03 11:58 ` Philip Herron
@ 2021-06-03 12:05   ` John Paul Adrian Glaubitz
  2021-06-03 12:10     ` Philip Herron
  2021-06-03 19:05   ` Mark Wielaard
  1 sibling, 1 reply; 6+ messages in thread
From: John Paul Adrian Glaubitz @ 2021-06-03 12:05 UTC (permalink / raw)
  To: Philip Herron; +Cc: gcc-rust

Hi Phil!

On 6/3/21 1:58 PM, Philip Herron wrote:
> 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?
Sounds like a great idea. I think another idea would be to set up Travis which
has support for a couple of architectures such as aarch64 and ppc64le.

I'm not planning to keep repeating this manual build and testsuite runs, but I
just want to get familiar with the project and fix some minor portability issues
while I'm at it.

I'm also particularly interested to see how well gccrs already works on various
architectures. Getting Rust to work on more targets is very important for Debian
as we have some architectures which are currently falling behind due to the lack
of platform support in rustc.

Adrian 

-- 
 .''`.  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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Test results for gccrs on Debian unstable aarch64
  2021-06-03 12:05   ` John Paul Adrian Glaubitz
@ 2021-06-03 12:10     ` Philip Herron
  0 siblings, 0 replies; 6+ messages in thread
From: Philip Herron @ 2021-06-03 12:10 UTC (permalink / raw)
  To: John Paul Adrian Glaubitz; +Cc: gcc-rust

[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]

That's likely a better solution. In fact, I started looking at that a while
back, but I haven't test/finished it:

```
language: c

arch:
  - amd64
  - ppc64le
  - s390x
  - arm64

os: linux

before_install:
  - sudo apt-get install -y automake autoconf libtool autogen bison flex
libgmp3-dev libmpfr-dev libmpc-dev build-essential gcc-multilib
g++-multilib dejagnu

script:
  - mkdir -p gccrs-build;
  - cd gccrs-build; ../configure --enable-languages=rust
--disable-bootstrap --enable-multilib; make -j $(nproc); make check-rust
  - cd gccrs-build; \
           if grep "# of unexpected" gcc/testsuite/rust/rust.sum;\
           then \
              echo "some tests are not correct"; \
              exit 1; \
            else \
              exit 0; \
            fi

```

I might make an issue out of this, in the hopes someone can test and fix up
this initial travis.yml.

--Phil

On Thu, 3 Jun 2021 at 13:05, John Paul Adrian Glaubitz <
glaubitz@physik.fu-berlin.de> wrote:

> Hi Phil!
>
> On 6/3/21 1:58 PM, Philip Herron wrote:
> > 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?
> Sounds like a great idea. I think another idea would be to set up Travis
> which
> has support for a couple of architectures such as aarch64 and ppc64le.
>
> I'm not planning to keep repeating this manual build and testsuite runs,
> but I
> just want to get familiar with the project and fix some minor portability
> issues
> while I'm at it.
>
> I'm also particularly interested to see how well gccrs already works on
> various
> architectures. Getting Rust to work on more targets is very important for
> Debian
> as we have some architectures which are currently falling behind due to
> the lack
> of platform support in rustc.
>
> Adrian
>
> --
>  .''`.  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
>

[-- Attachment #2: Type: text/html, Size: 3001 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Test results for gccrs on Debian unstable aarch64
  2021-06-03 11:58 ` Philip Herron
  2021-06-03 12:05   ` John Paul Adrian Glaubitz
@ 2021-06-03 19:05   ` Mark Wielaard
  2021-06-03 22:16     ` Mark Wielaard
  1 sibling, 1 reply; 6+ messages in thread
From: Mark Wielaard @ 2021-06-03 19:05 UTC (permalink / raw)
  To: Philip Herron; +Cc: John Paul Adrian Glaubitz, gcc-rust

On Thu, Jun 03, 2021 at 12:58:46PM +0100, Philip Herron wrote:
> 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

Note that the buildbot could provide that (for the arches it supports).
If you look at:
https://builder.wildebeest.org/buildbot/#/builders?tags=gccrust
you can see which arches are green.
And for each build it publishes the rust.sum and rust.log files
(under the make check link)

Currently I have only enabled the arches that I know are fully green
(x86_64, arm64 and ppc64le). I should add ppc64[be] because that
should also be fully green. I am not sure about enabling enabling
others (arm32, i386 and s390x). It seems a bit pointless to run builds
we know are currently broken.

Cheers,

Mark

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Test results for gccrs on Debian unstable aarch64
  2021-06-03 19:05   ` Mark Wielaard
@ 2021-06-03 22:16     ` Mark Wielaard
  0 siblings, 0 replies; 6+ messages in thread
From: Mark Wielaard @ 2021-06-03 22:16 UTC (permalink / raw)
  To: Philip Herron; +Cc: John Paul Adrian Glaubitz, gcc-rust

Hi,

On Thu, Jun 03, 2021 at 09:05:22PM +0200, Mark Wielaard wrote:
> Currently I have only enabled the arches that I know are fully green
> (x86_64, arm64 and ppc64le). I should add ppc64[be] because that
> should also be fully green.

fedora-ppc64 is enabled now too:
https://builder.wildebeest.org/buildbot/#/builders/61

It currently has no builds because there have been no new commits,
but I verified by hand that it is green.

Cheers,

Mark


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-06-03 22:16 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-03 11:28 Test results for gccrs on Debian unstable aarch64 John Paul Adrian Glaubitz
2021-06-03 11:58 ` Philip Herron
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

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).