public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
* [Linaro-TCWG-CI] gdb-14-branchpoint-560-g57e6a098ae5: FAIL: 2 regressions on aarch64
@ 2023-12-03 16:34 ci_notify
  0 siblings, 0 replies; only message in thread
From: ci_notify @ 2023-12-03 16:34 UTC (permalink / raw)
  To: kevinb; +Cc: gdb-testers

[-- Attachment #1: Type: text/plain, Size: 3091 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 track this report status in https://linaro.atlassian.net/browse/GNU-1059 , please let us know if you are looking at the problem and/or when you have a fix.

In gdb_check master-aarch64 after:

  | commit gdb-14-branchpoint-560-g57e6a098ae5
  | Author: Kevin Buettner <kevinb@redhat.com>
  | Date:   Sat Dec 2 20:25:31 2023 -0700
  | 
  |     Fix detach bug when lwp has exited/terminated
  |     
  |     When using GDB on native linux, it can happen that, while attempting
  |     to detach an inferior, the inferior may have been exited or have been
  |     killed, yet still be in the list of lwps.  Should that happen, the
  |     assert in x86_linux_update_debug_registers in
  |     gdb/nat/x86-linux-dregs.c will trigger.  The line in question looks
  | ... 106 lines of the commit log omitted.

FAIL: 2 regressions

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

Running gdb:gdb.base/kill-during-detach.exp ...
FAIL: gdb.base/kill-during-detach.exp: exit_p=false: checkpoint_p=true: python kill_and_detach()
FAIL: gdb.base/kill-during-detach.exp: exit_p=true: checkpoint_p=true: python kill_and_detach()

		=== Results Summary ===

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

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

-----------------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-aarch64-build/544/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/542/artifact/artifacts

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

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

List of configurations that regressed due to this commit :
* tcwg_gdb_check
** master-aarch64
*** FAIL: 2 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/57e6a098ae51df8162ad5c5689d1a1e09c6f9a66/tcwg_gdb_check/master-aarch64/details.txt
*** https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/544/

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-12-03 16:34 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-03 16:34 [Linaro-TCWG-CI] gdb-14-branchpoint-560-g57e6a098ae5: FAIL: 2 regressions on aarch64 ci_notify

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