Hi Guinevere, Linaro CI has very consistently identified same failures in patches 1/8, 2/8, 3/8, 4/8, and 5/8 of your patch series for both aarch32-linux and aarch64-linux targets. Starting with patch 6/8 testing passes for both aarch32-linux and aarch64-linux. Also, no other patches in [1] show same failure pattern as your patch series.
It's possible that there is a problem with Linaro CI, but your patch [2] seems like a likely culprit. Maybe it's missing a part that's later added in 6/8? Please let me know if it still looks like a CI failure, and I'll investigate more. Thanks! [1] https://patchwork.sourceware.org/project/gdb/list/ [2] https://patchwork.sourceware.org/project/gdb/patch/[email protected]/ -- Maxim Kuvyrkov https://www.linaro.org > On Jun 8, 2026, at 16:26, Guinevere Larsen via linaro-toolchain > <[email protected]> wrote: > > Hi! > > This seems to be an issue with your testing infrastructure. These patches > have not touched anything that isn't related to record-full so there's no way > they could be causing failures in gdb.arch tests. I guess this test is no > longer reliable. > > -- > Cheers, > Guinevere Larsen > It/she > > > On 6/7/26 3:44 AM, [email protected] wrote: >> Dear contributor, >> >> Our automatic CI has detected problems related to your patch(es). Please >> find some details below. >> >> In gdb_check master-arm, after: >> | 3 patches in gdb >> | Patchwork URL: https://patchwork.sourceware.org/patch/136305 >> | 1f3856ef4e9 [PATCH v4 3/8] gdb/record: remove record_full_insn_num >> | 9165d18a941 [PATCH v4 2/8] gdb/record: factor out reading and writing >> the execution log to corefile >> | 85ad6ec91da [PATCH v4 1/8] gdb/record: Refactor record history >> | ... applied on top of baseline commit: >> | 4562eab73d3 Automatic date update in version.in >> >> Produces 171 regressions: >> | >> | regressions.sum: >> | Running gdb:gdb.arch/skip-prologue.exp ... >> | FAIL: gdb.arch/skip-prologue.exp: f2: $\bp_addr == $\prologue_end_addr >> (skipped too much) >> | FAIL: gdb.arch/skip-prologue.exp: f4: $\bp_addr == $\prologue_end_addr >> (skipped too much) >> | Running gdb:gdb.arch/thumb2-it.exp ... >> | FAIL: gdb.arch/thumb2-it.exp: it_3, stepi 3 >> | ... and 187 more >> >> Used configuration : >> *CI config* tcwg_gdb_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 >> [email protected] 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_gdb_check--master-arm-precommit/builds/10298/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_gdb_check--master-arm-precommit/builds/10298/archive/artifacts/artifacts.precommit/notify/ >> The list of [ignored] baseline and flaky failures are in >> * >> http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/10298/archive/artifacts/artifacts.precommit/sumfiles/xfails.xfail >> >> Current build : >> http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/10298/archive/artifacts/ >> Reference build : >> http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-build/builds/10211/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. > > _______________________________________________ > linaro-toolchain mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ linaro-toolchain mailing list -- [email protected] To unsubscribe send an email to [email protected]
