Hi, For this V2-patch, I got the same "Operation not permitted" errors as for the V1 one: https://lists.linaro.org/archives/list/linaro-toolchain@lists.linaro.org/thread/2EHTRTCZHLDJZXZ46MLNTNVGZNPKX6UY/
@Adhemerval: have you had a look? The only non-s390x changes of my patch are in: elf/Makefile elf/tst-glibc-hwcaps-cache.script => There the libmarkermod6 libraries are added. As I don't have an arm, I've checked on x86_64, that the testcase elf/tst-glibc-hwcaps-cache.c contains the libmarkermod6.so files in glibc-hwcaps/z13-z17 directories by adding a "ldconfig -p" to the test. Any idea why those "Operation not permitted" regressions hits my patch, but no others? Bye, Stefan On 4/30/25 20:19, ci_not...@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/111247 > | Author: Stefan Liebler <s...@linux.ibm.com> > | Date: Tue Apr 29 13:28:58 2025 +0200 > | > | [PATCH v2] S390: Add new s390 platform z17. > | > | Hi, > | need a V2: stfle_bits on stack in init_cpu_features_no_tunables() > needs to be > | zeroed before usage. If there is no more feedback, I will commit > this patch shortly. > | ... 41 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 84977600dac math: Fix UB on sinpif (BZ 32925) > > 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 > * > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/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_glibc_check--master-arm-precommit/3574/artifact/artifacts/artifacts.precommit/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > > Current build : > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2743/artifact/artifacts > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
