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.or
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 resu
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 libmpf
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
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
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.ex
