Sergio,
The AArch64 Buildbot has been switched to new hardware.
We’re now running on a Huawei 1616 AArch64 with Ubuntu 18.04.
That should get rid of the random build failures (which were due to
RAM errors).
Couple of things to note:
1) This is Ubuntu 18.04, not Ubuntu 16.04, which means the slave
name "ubuntu16-aarch64” should probably be updated at some point.
2) There are a bunch of new failures, jumping from 111 to 197.
This is due to moving to Ubuntu18. For example, dump.exp is broken
due to executables being mapped at a much higher address range
(Because GCC is now using --enable-default-pie). I’ll look into
fixing them.
3) The Ubuntu-Aarch64-native-gdbserver-m64 queue is probably still a
little racy. I think I’ve got a fix for this - will post later this
week.
4) The Ubuntu-Aarch64-native-extended-gdbserver-m64 continues
to timeout after 90minutes due to hanging tests. However, looking at
Fedora-x86_64-native-extended-gdbserver-m64, that is sometimes
taking 4 hours to pass! On my local machine, it looks like it is
hanging. I’ll try and look into this soon.
5) The -j16 should probably be increased. It’s a 64 core box, so
If we double to -j32 that should keep half the machine free for
glibc buildbot the machine is shared with. Increasing it might
make point 3 a little worse - but might stop the timeouts on 4.
6) There might be a little bit of downtime later this week as
DNS stuff gets switched.
Alan.