public inbox for gdbadmin@sourceware.org
help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Linaro Toolchain Working Group
	<linaro-toolchain@lists.linaro.org>,
	Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
	gdbadmin@sourceware.org, gdb-testers@sourceware.org
Subject: Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1426-gb960445a459: FAIL: 1 regressions on arm
Date: Wed, 31 Jan 2024 11:15:25 +0400	[thread overview]
Message-ID: <EA23A47E-A0AE-4769-B510-F52F479B1DDA@linaro.org> (raw)
In-Reply-To: <1950113685.1112.1706650248017@jenkins.jenkins>

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



  reply	other threads:[~2024-01-31  7:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 21:30 ci_notify
2024-01-31  7:15 ` Maxim Kuvyrkov [this message]
2024-01-31 15:36   ` Thiago Jung Bauermann

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=EA23A47E-A0AE-4769-B510-F52F479B1DDA@linaro.org \
    --to=maxim.kuvyrkov@linaro.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-testers@sourceware.org \
    --cc=gdbadmin@sourceware.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=thiago.bauermann@linaro.org \
    /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).