ci_notify@linaro.org writes:
After gdb-13-branchpoint-527-g46758593515 commit 4675859351582f017b495ff13fb2ea72a99834af Author: Tom Tromey tom@tromey.com
Rename to allow_ifunc_tests
This is a GDB commit so I had a look at this failure. The commit can't be responsible for it though, because it only changes some .exp files in the GDB testsuite.
the following benchmarks slowed down by more than 3%:
- 465.tonto failed to build
I couldn't find the actual build failure in the job artifacts, so I ran the instructions for reproducing the failure on my dev container in tcwg-jade-03. It did fail, but with a slightly different error:
416.gamess failed to build.
I suppose this is GCC's test gcc/testsuite/gfortran.dg/fmt_read_5.f, so I went to directory abe/builds/aarch64-unknown-linux-gnu/aarch64-linux-gnu/gcc-gcc.git~master-stage2/gcc and ran:
$ make check-fortran RUNTESTFLAGS=dg.exp=fmt_read_5.f
Which passed, so I'm stuck now.
Regarding the failure of 465.tonto in the original CI report, I couldn't find any GCC test that could be related to it.