Hello, Christophe Lyon <christophe.l...@linaro.org> writes:
> On Tue, 1 Apr 2025 at 07:22, Martin Simmons <qqxnjvamv...@dyxyl.com> wrote: >> >> >>>>> On Sun, 30 Mar 2025 23:58:18 +0000 (UTC), ci notify said: >> > ... >> > In gdb_check master-aarch64, after: >> > | gdb patch https://patchwork.sourceware.org/patch/109371 >> > ... >> > Used configuration : >> > *CI config* tcwg_gdb_check master-aarch64 >> > *configure and test flags:* none, autodetected on >> > aarch64-unknown-linux-gnu >> > >> > If you have any questions regarding this report, please ask on >> > linaro-toolchain@lists.linaro.org mailing list. >> > >> > -----------------8<--------------------------8<--------------------------8<-------------------------- >> > >> > The information below contains the details of the failures, and the ways >> > to reproduce >> > a debug environment: >> > >> > You can find the failure logs in *.log.1.xz files in >> > * >> > https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/artifact/artifacts/artifacts.precommit/00-sumfiles/ >> > The full lists of regressions and improvements as well as configure and >> > make commands >> > are in >> > * >> > https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/artifact/artifacts/artifacts.precommit/notify/ >> > The list of [ignored] baseline and flaky failures are in >> > * >> > https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail >> > >> > Current build : >> > https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/artifact/artifacts >> > Reference build : >> > https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/2461/artifact/artifacts >> >> In >> https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/artifact/artifacts/artifacts.precommit/00-sumfiles/gdb.log.1.xz >> it appears that the "info set" test started at line 1159 and failed with >> >> FAIL: gdb.base/default.exp: info set (timeout) >> >> at line 1533. Then a few more tests failed with timeout and finally >> over 100 tests failed with no obvious reason. >> >> Was this caused by a problem on the CI machine? > > Hi, > Thanks for the heads-up. > > I'm not aware of any problem with that CI machine, although it's > slightly slower than others we have. > > We do have a system to detect "flaky" tests, so this should normally > be excluded. > > Maybe Thiago has already noticed random results with this particular test? > Maybe it just needs an extended timeout factor to cope with large > numbers of environment variables? Yes, default.exp has a lot of flaky failures and they are normally discounted by our flaky detection system. The problem was that we recently lost history for the tcwg_gdb_check job and the system is still redetecting the flaky tests. Sorry about the false regression report. -- Thiago _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
