Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In glibc_check master-arm, after: | glibc patch https://patchwork.sourceware.org/patch/132824 | Author: Moritz Klammler | Date: Tue Apr 7 21:36:12 2026 +0200 | | [PATCH 1/1] nptl: Propagate EDEADLK from FUTEX_LOCK_PI for errror-checking and recursive mutexes | | This patch changes the behavior of pthread_mutex_lock for error-checking and | recursive PI mutexes in case of non-trivial deadlock. The user-space code | doesn't detect the case where two or more threads would mutually deadlock each | ... 19 lines of the commit log omitted. | ... applied on top of baseline commit: | dfb150f3aa math: Add fast-path to fma 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 * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10066/archive/artifacts/artifacts.precommit/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10066/archive/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10066/archive/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10066/archive/artifacts/ Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10055/archive/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.