public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: tromey@adacore.com
Cc: gdb-testers@sourceware.org,
	Linaro Toolchain Working Group
	<linaro-toolchain@lists.linaro.org>
Subject: Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm
Date: Mon, 11 Mar 2024 19:56:19 +0400	[thread overview]
Message-ID: <29B97042-BA6A-4EFB-8999-F4D35D8F1FC9@linaro.org> (raw)
In-Reply-To: <46425511.13456.1706361902239@jenkins.jenkins>

> 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



  reply	other threads:[~2024-03-11 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27 13:25 ci_notify
2024-03-11 15:56 ` Maxim Kuvyrkov [this message]
2024-03-11 20:14   ` Tom Tromey
2024-03-12 13:57     ` Maxim Kuvyrkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29B97042-BA6A-4EFB-8999-F4D35D8F1FC9@linaro.org \
    --to=maxim.kuvyrkov@linaro.org \
    --cc=gdb-testers@sourceware.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=tromey@adacore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).