Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In glibc_check master-aarch64, after: | glibc patch https://patchwork.sourceware.org/patch/132009 | Author: Xi Ruoyao | Date: Fri Mar 20 17:12:34 2026 +0800 | | [PATCH v2] LoongArch: fix missing trap for enabled exceptions on narrowing operation | | The libc_feupdateenv_test macro is supposed to trap when the trap for a | previously held exception is enabled. But | libc_feupdateenv_test_loongarch wasn't doing it properly: the comment | ... 8 lines of the commit log omitted. | ... applied on top of baseline commit: | 19781c22211 math: Fix spurious overflow and missing errno for lgammaf Used configuration : *CI config* tcwg_glibc_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_glibc_check--master-aarch64-precommit/4171/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-aarch64-precommit/4171/artifact/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/4171/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/4171/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/3440/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.