Hi,
I've looked into tests.log.1.xz and there are plenty of "Operation not permitted" errors. I don't think that this has something to do with my patch? Can you please check on your side, if there was a change/issue on the build system?
Bye, Stefan
On 4/16/25 13:32, ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-arm, after: | glibc patch https://patchwork.sourceware.org/patch/110503 | Author: Stefan Liebler stli@linux.ibm.com | Date: Tue Apr 15 16:52:17 2025 +0200 | | [PATCH] S390: Add new s390 platform z17. | | The glibc-hwcaps subdirectories are extended by "z17". Libraries are loaded if | the z17 facility bits are active: | - Miscellaneous-instruction-extensions facility 4 | ... 35 lines of the commit log omitted. | ... applied on top of baseline commit: | ceeffd970c5 aarch64: Add back non-temporal load/stores from oryon-1's memset
Produces 90 regressions: | | regressions.sum: | Running glibc:debug ... | FAIL: debug/tst-fortify-syslog | Running glibc:dirent ... | FAIL: dirent/tst-readdir-long | FAIL: dirent/tst-readdir-zero-inode | ... and 99 more
Used configuration : *CI config* tcwg_glibc_check master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
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
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artifa... Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2681/artifact/a...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.