Hi Arjun,
Please ignore this report. We had a new machine added to the testing pool, and it behaved differently than the others.
-- Maxim Kuvyrkov https://www.linaro.org
On Oct 4, 2023, at 22:30, ci_notify@linaro.org wrote:
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
In CI config tcwg_glibc_check/master-arm after:
| 13 patches in glibc | Patchwork URL: https://patchwork.sourceware.org/patch/76970 | 72a0ec189c Move 'rpc' routines from 'inet' into 'nss' | e9e10ad39b Move 'protocols' routines from 'inet' into 'nss' | e0694af485 Move 'networks' routines from 'inet' into 'nss' | 547bcf6d44 Move 'netgroup' routines from 'inet' into 'nss' | 6c43eb641a Move 'hosts' routines from 'inet' into 'nss' | ... and 8 more patches in glibc | ... applied on top of baseline commit: | 1056e5b4c3 tunables: Terminate if end of input is reached (CVE-2023-4911)
FAIL: 7 regressions
regressions.sum: === glibc tests ===
Running glibc:io ... FAIL: io/tst-close_range
Running glibc:misc ... FAIL: misc/tst-epoll FAIL: misc/tst-epoll-time64 FAIL: misc/tst-mount FAIL: misc/tst-process_mrelease ... and 6 more entries
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and progressions are in
The list of [ignored] baseline and flaky failures are in
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/802/artifac... Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/650/artifact/ar...
linaro-toolchain@lists.linaro.org
-
Maxim Kuvyrkov