[Linaro-TCWG-CI] gdb-14-branchpoint-1426-gb960445a459: FAIL: 1 regressions on arm

[Linaro-TCWG-CI] gdb-14-branchpoint-1426-gb960445a459: FAIL: 1 regressions on arm

[ci_notify]

[-- Attachment #1: Type: text/plain, Size: 2709 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-1137 , please let us know if you are looking at the problem and/or when you have a fix.

In gdb_check master-arm after:

  | commit gdb-14-branchpoint-1426-gb960445a459
  | Author: GDB Administrator <gdbadmin@sourceware.org>
  | Date:   Tue Jan 30 00:00:26 2024 +0000
  | 
  |     Automatic date update in version.in

FAIL: 1 regressions

regressions.sum:
		=== gdb tests ===

Running gdb:gdb.threads/staticthreads.exp ...
FAIL: gdb.threads/staticthreads.exp: up 10


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

The configuration of this build is:
CI config tcwg_gdb_check master-arm

-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:

Current build   : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/751/artifact/artifacts

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

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

List of configurations that regressed due to this commit :
* tcwg_gdb_check
** master-arm
*** FAIL: 1 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/b960445a45981873c5b1718824ea9d3b5749433a/tcwg_gdb_check/master-arm/details.txt
*** https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts

Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1426-gb960445a459: FAIL: 1 regressions on arm

[Maxim Kuvyrkov]

Hi All,

This is a false positive, obviously.  We do our best to filter out flaky tests, but in this case "gdb.threads/staticthreads.exp: up 10" PASSed twice in the previous run, and then FAILed twice in the next run.  Sneaky!

Re. the FAIL, the testcase expects to be " in main .*" after "up 10", but ends up in pthread_join() instead:
===
up 10
#4  0x0001b864 in pthread_join ()
(gdb) FAIL: gdb.threads/staticthreads.exp: up 10
===
See [1] for details.

[1] https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/00-sumfiles/gdb.log.1.xz .

Hi Thiago,

Would you please investigate whether ending up in pthread_join() is expected/reasonable for 32-bit ARM?  In other words, whether we have a GDB bug exposed by staticthreads.exp or the testcase needs to be generalized a bit.

Thank you,

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

> On Jan 31, 2024, at 01:30, 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-1137 , please let us know if you are looking at the problem and/or when you have a fix.
> 
> In gdb_check master-arm after:
> 
>  | commit gdb-14-branchpoint-1426-gb960445a459
>  | Author: GDB Administrator <gdbadmin@sourceware.org>
>  | Date:   Tue Jan 30 00:00:26 2024 +0000
>  | 
>  |     Automatic date update in version.in
> 
> FAIL: 1 regressions
> 
> regressions.sum:
> === gdb tests ===
> 
> Running gdb:gdb.threads/staticthreads.exp ...
> FAIL: gdb.threads/staticthreads.exp: up 10
> 
> 
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/00-sumfiles/
> The full lists of regressions and progressions as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/sumfiles/xfails.xfail
> 
> The configuration of this build is:
> CI config tcwg_gdb_check master-arm
> 
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
> 
> Current build   : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/751/artifact/artifacts
> 
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/b960445a45981873c5b1718824ea9d3b5749433a/tcwg_gdb_check/master-arm/reproduction_instructions.txt
> 
> Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=b960445a45981873c5b1718824ea9d3b5749433a
> 
> List of configurations that regressed due to this commit :
> * tcwg_gdb_check
> ** master-arm
> *** FAIL: 1 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/b960445a45981873c5b1718824ea9d3b5749433a/tcwg_gdb_check/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts

Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1426-gb960445a459: FAIL: 1 regressions on arm

[Thiago Jung Bauermann]

Hello,

This is recorded as GDB bug #31254¹. I've been investigating it and
yesterday I realised it's a memory corruption issue in a data structure
used by the Arm unwinder which uses exception tables.

I hope to have a fix for it soon™.

¹ https://sourceware.org/bugzilla/show_bug.cgi?id=31254


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

> Hi All,
>
> This is a false positive, obviously.  We do our best to filter out flaky tests, but in
> this case "gdb.threads/staticthreads.exp: up 10" PASSed twice in the previous run, and
> then FAILed twice in the next run.  Sneaky!
>
> Re. the FAIL, the testcase expects to be " in main .*" after "up 10", but ends up in
> pthread_join() instead:
> ===
> up 10
> #4  0x0001b864 in pthread_join ()
> (gdb) FAIL: gdb.threads/staticthreads.exp: up 10
> ===
> See [1] for details.
>
> [1]
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/00-sumfiles/gdb.log.1.xz
> .
>
> Hi Thiago,
>
> Would you please investigate whether ending up in pthread_join() is expected/reasonable
> for 32-bit ARM?  In other words, whether we have a GDB bug exposed by staticthreads.exp or
> the testcase needs to be generalized a bit.
>
> Thank you,


-- 
Thiago