On Jan 27, 2024, at 17:25, ci_notify@linaro.org wrote:
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1121 , please let us know if you are looking at the problem and/or when you have a fix.
In master-arm after:
| commit gdb-14-branchpoint-1356-g7737b133640 | Author: Tom Tromey tromey@adacore.com | Date: Tue Jan 9 11:47:17 2024 -0700 | | Handle DW_AT_endianity on enumeration types | | A user found that gdb would not correctly print a field from an Ada | record using the scalar storage order feature. We tracked this down | to a combination of problems. | | First, GCC did not emit DW_AT_endianity on the enumeration type. | ... 14 lines of the commit log omitted.
FAIL: 1 regressions
regressions.sum: === gdb tests ===
Running gdb:gdb.ada/scalar_storage.exp ... FAIL: gdb.ada/scalar_storage.exp: print V_BE
Hi Tom,
I see the above failure for both aarch64-linux-gnu and arm-linux-gnueabihf in our testing. The log shows ([1]): === Breakpoint 1, storage () at /home/tcwg-buildslave/workspace/tcwg_gnu_2/gdb/gdb/testsuite/gdb.ada/scalar_storage/storage.adb:53 53 Do_Nothing (V_LE'Address); -- START (gdb) print V_LE $1 = (value => 126, another_value => 12, color => green) (gdb) PASS: gdb.ada/scalar_storage.exp: print V_LE get_compiler_info: gcc-14-0-1 print V_BE $2 = (value => 126, another_value => 12, color => red) (gdb) FAIL: gdb.ada/scalar_storage.exp: print V_BE ===
Any idea what can be causing this?
This failure happens in CI configurations where we track tip-of-trunk GCC.
[1] https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/la...
Thanks,
-- Maxim Kuvyrkov https://www.linaro.org
=== Results Summary ===
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and progressions are in
The list of [ignored] baseline and flaky failures are in
The configuration of this build is: CI config tcwg_gnu_native_check_gdb master-arm
-----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/a... Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1075/a...
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha...
Full commit : https://sourceware.org/git/?p=binutils-gdb.git%3Ba=commitdiff%3Bh=7737b13364...
List of configurations that regressed due to this commit :
- tcwg_gnu_native_check_gdb
** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha... *** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/a...