public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: ci_notify@linaro.org
To: simon.marchi@efficios.com
Cc: gdb-testers@sourceware.org
Subject: [Linaro-TCWG-CI] gdb-14-branchpoint-108-g8971d2788e7: FAIL: 20 regressions on arm
Date: Thu, 19 Oct 2023 21:09:51 +0000 (UTC)	[thread overview]
Message-ID: <278522831.44119.1697749792548@jenkins.jenkins> (raw)

[-- Attachment #1: Type: text/plain, Size: 3327 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.

In  master-arm after:

  | commit gdb-14-branchpoint-108-g8971d2788e7
  | Author: Simon Marchi <simon.marchi@efficios.com>
  | Date:   Thu Oct 19 10:55:38 2023 -0400
  | 
  |     gdb: link so_list using intrusive_list
  |     
  |     Replace the hand-made linked list implementation with intrusive_list,
  |     simplying management of list items.
  |     
  |     Change-Id: I7f55fd88325bb197cc655c9be5a2ec966d8cc48d
  |     Approved-By: Pedro Alves <pedro@palves.net>
  | ... 1 lines of the commit log omitted.

FAIL: 20 regressions

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

Running gdb:gdb.base/break-idempotent.exp ...
ERROR: GDB process no longer exists
ERROR: breakpoints not deleted
ERROR: can not find channel named "exp8"
UNRESOLVED: gdb.base/break-idempotent.exp: pie=pie: always_inserted=off: hbreak: file $binfile
UNRESOLVED: gdb.base/break-idempotent.exp: pie=pie: always_inserted=off: hbreak: condition $bpnum cond_global == 0
UNRESOLVED: gdb.base/break-idempotent.exp: pie=pie: always_inserted=off: hbreak: delete all breakpoints in delete_breakpoints
UNRESOLVED: gdb.base/break-idempotent.exp: pie=pie: always_inserted=off: hbreak: b bar
... and 15 more entries

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

The configuration of this build is:
CI config tcwg_gnu_native_fast_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_fast_check_gdb--master-arm-build/513/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_fast_check_gdb--master-arm-build/512/artifact/artifacts

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

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

Latest bug report status : https://linaro.atlassian.net/browse/GNU-971

List of configurations that regressed due to this commit :
* tcwg_gnu_native_fast_check_gdb
** master-arm
*** FAIL: 20 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/8971d2788e79db2ffc1205ed36935483eedf2fab/tcwg_gnu_native_fast_check_gdb/master-arm/details.txt
*** https://ci.linaro.org/job/tcwg_gnu_native_fast_check_gdb--master-arm-build/513/

                 reply	other threads:[~2023-10-19 21:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=278522831.44119.1697749792548@jenkins.jenkins \
    --to=ci_notify@linaro.org \
    --cc=gdb-testers@sourceware.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=simon.marchi@efficios.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).