public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm
@ 2024-01-27 13:25 ci_notify
  2024-03-11 15:56 ` Maxim Kuvyrkov
  0 siblings, 1 reply; 4+ messages in thread
From: ci_notify @ 2024-01-27 13:25 UTC (permalink / raw)
  To: tromey; +Cc: gdb-testers

[-- Attachment #1: Type: text/plain, Size: 3129 bytes --]

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

		=== Results Summary ===

You can find the failure logs in *.log.1.xz files in
 - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts/00-sumfiles/ .
The full lists of regressions and progressions are in
 - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts/notify/ .
The list of [ignored] baseline and flaky failures are in
 - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts/sumfiles/xfails.xfail .

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/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1075/artifact/artifacts

Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/7737b1336402cd4682538620ab996bdb7ad0ea79/tcwg_gnu_native_check_gdb/master-arm/reproduction_instructions.txt

Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=7737b1336402cd4682538620ab996bdb7ad0ea79

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/sha1/7737b1336402cd4682538620ab996bdb7ad0ea79/tcwg_gnu_native_check_gdb/master-arm/details.txt
*** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm
  2024-01-27 13:25 [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm ci_notify
@ 2024-03-11 15:56 ` Maxim Kuvyrkov
  2024-03-11 20:14   ` Tom Tromey
  0 siblings, 1 reply; 4+ messages in thread
From: Maxim Kuvyrkov @ 2024-03-11 15:56 UTC (permalink / raw)
  To: tromey; +Cc: gdb-testers, Linaro Toolchain Working Group

> 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/lastSuccessfulBuild/artifact/artifacts/00-sumfiles/gdb.log.xz

Thanks,

--
Maxim Kuvyrkov
https://www.linaro.org


> 
> === Results Summary ===
> 
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts/sumfiles/xfails.xfail .
> 
> 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/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1075/artifact/artifacts
> 
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/7737b1336402cd4682538620ab996bdb7ad0ea79/tcwg_gnu_native_check_gdb/master-arm/reproduction_instructions.txt
> 
> Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=7737b1336402cd4682538620ab996bdb7ad0ea79
> 
> 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/sha1/7737b1336402cd4682538620ab996bdb7ad0ea79/tcwg_gnu_native_check_gdb/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/artifact/artifacts



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm
  2024-03-11 15:56 ` Maxim Kuvyrkov
@ 2024-03-11 20:14   ` Tom Tromey
  2024-03-12 13:57     ` Maxim Kuvyrkov
  0 siblings, 1 reply; 4+ messages in thread
From: Tom Tromey @ 2024-03-11 20:14 UTC (permalink / raw)
  To: Maxim Kuvyrkov; +Cc: tromey, gdb-testers, Linaro Toolchain Working Group

>>>>> Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> writes:

>> | 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.

> I see the above failure for both aarch64-linux-gnu and
> arm-linux-gnueabihf in our testing.  The log shows ([1]):

> (gdb) PASS: gdb.ada/scalar_storage.exp: print V_LE
> get_compiler_info: gcc-14-0-1

> Any idea what can be causing this?

> This failure happens in CI configurations where we track tip-of-trunk GCC.

This failure is what I would expect if your compiler does not have the
fix.  Can you see if your gcc includes this change?

commit 5d8b60effc7268448a94fbbbad923ab6871252cd
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Wed Jan 10 13:23:46 2024 +0100

    Fix debug info for enumeration types with reverse Scalar_Storage_Order
    
    This implements the support of DW_AT_endianity for enumeration types because
    they are scalar and therefore, reverse Scalar_Storage_Order is supported for
    them, but only when the -gstrict-dwarf switch is not passed because this is
    an extension.
    
    There is an associated GDB patch to be submitted to grok the new DWARF.

thanks,
Tom

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm
  2024-03-11 20:14   ` Tom Tromey
@ 2024-03-12 13:57     ` Maxim Kuvyrkov
  0 siblings, 0 replies; 4+ messages in thread
From: Maxim Kuvyrkov @ 2024-03-12 13:57 UTC (permalink / raw)
  To: Tom Tromey; +Cc: gdb-testers, Linaro Toolchain Working Group

> On Mar 12, 2024, at 00:14, Tom Tromey <tromey@adacore.com> wrote:
> 
>>>>>> Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> writes:
> 
>>> | 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.
> 
>> I see the above failure for both aarch64-linux-gnu and
>> arm-linux-gnueabihf in our testing.  The log shows ([1]):
> 
>> (gdb) PASS: gdb.ada/scalar_storage.exp: print V_LE
>> get_compiler_info: gcc-14-0-1
> 
>> Any idea what can be causing this?
> 
>> This failure happens in CI configurations where we track tip-of-trunk GCC.
> 
> This failure is what I would expect if your compiler does not have the
> fix.  Can you see if your gcc includes this change?
> 
> commit 5d8b60effc7268448a94fbbbad923ab6871252cd
> Author: Eric Botcazou <ebotcazou@adacore.com>
> Date:   Wed Jan 10 13:23:46 2024 +0100
> 
>    Fix debug info for enumeration types with reverse Scalar_Storage_Order

Ah, now I understand.  While we do have the above commit in our GCC sources (we build tip-of-trunk in this CI configuration), we don't enable ada language.  So testsuite harness detects GCC version as 14.0 and enables the test, but actual gnat compiler is used from the distro package, which is much older.

We will consider enabling ada language in our CI builds, which should fix this.

Thanks for helping troubleshooting this!

--
Maxim Kuvyrkov
https://www.linaro.org



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-03-12 13:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-27 13:25 [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm ci_notify
2024-03-11 15:56 ` Maxim Kuvyrkov
2024-03-11 20:14   ` Tom Tromey
2024-03-12 13:57     ` Maxim Kuvyrkov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).