On 4/30/25 06:18, ci_notify@linaro.org 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: | gdb patch https://patchwork.sourceware.org/patch/111028 | Author: Tom de Vries tdevries@suse.de | Date: Fri Apr 25 17:13:32 2025 +0200 | | [PATCH v2] [gdb/testsuite] Simplify gdb.tui/tui-layout-asm.exp | | On x86_64-cygwin, with test-case gdb.tui/tui-layout-asm.exp I run into: | ... | WARNING: The following failure is probably due to the TUI window | ... 49 lines of the commit log omitted. | ... applied on top of baseline commit: | 48d0ac705c4 Handle base type without DW_AT_byte_size
Produces 2 regressions: | | regressions.sum: | Running gdb:gdb.python/py-missing-objfile.exp ... | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_exec_var | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_lib_var
The FAILs are obviously unrelated to the patch which modifies a different test-case.
But anyway, this a know PR ( https://sourceware.org/bugzilla/show_bug.cgi?id=32445 ).
I've just committed a fix.
Thanks, - Tom
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 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
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifact... Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/2666/artifact/art...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.