Dear contributor, Our automatic CI successfully passed with your patch(es). Please find some details below. In gdb_check master-aarch64, after: | 12 patches in gdb | Patchwork URL: https://patchwork.sourceware.org/patch/130417 | 1b18b660557 [PATCH 12/13] gdb/dwarf: use (section, offset-in-section) as key for line_header hash | eb9b01eb5e1 [PATCH 11/13] gdb/dwarf: use (section, offset) as stmt_list key | 18835b619cf [PATCH 10/13] gdb/dwarf: store dwarf2_cus in expansion queue | 849da1fdbf5 [PATCH 09/13] gdb/dwarf: inline queue_and_load_dwo_tu | 252109a6ae0 [PATCH 08/13] gdb/dwarf: return dwarf2_cu from load_full_{comp, type}_unit | ... and 7 more patches in gdb | ... applied on top of baseline commit: | 130abadf1af gdb/testsuite: fix startup-hints.exp when running with -readnow Used configuration : *CI config* tcwg_gdb_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_gdb_check--master-aarch64-precommit/5441/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_gdb_check--master-aarch64-precommit/5441/artifact/artifacts/artifacts.precommit/notify/ The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/5441/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/5441/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/3190/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.