public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: linaro-toolchain@lists.linaro.org
Cc: nickc@redhat.com, gdb-testers@sourceware.org, tcwg-validation@linaro.org
Subject: Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1244-gfad00902c24: FAIL: 13 regressions: 13 progressions on arm
Date: Wed, 17 Jan 2024 14:23:20 -0300 [thread overview]
Message-ID: <87ttnb6fhz.fsf@linaro.org> (raw)
In-Reply-To: <176386515.1846.1705348516163@jenkins.jenkins>
Hello Nick,
ci_notify@linaro.org writes:
> In gdb_check master-arm after:
>
> | commit gdb-14-branchpoint-1244-gfad00902c24
> | Author: Nick Clifton <nickc@redhat.com>
> | Date: Mon Jan 15 12:25:00 2024 +0000
> |
> | nm: Replace --with-symbol-versions with --without-symbol-versions in --help output
> |
> | PR 31243
> | nm: Fix --help output
>
> FAIL: 13 regressions: 13 progressions
>
> regressions.sum:
> === gdb tests ===
>
> Running gdb:gdb.mi/mi-var-invalidate.exp ...
> ERROR: : spawn id exp8 not open
> ERROR: Couldn't send -var-info-type global_simple to GDB.
> ERROR: Couldn't send -var-info-type linteger to GDB.
> ERROR: Couldn't send -var-update global_simple to GDB.
> ERROR: Couldn't send -var-update linteger to GDB.
> ERROR: Process no longer exists
> ERROR: couldn't load outputs/gdb.mi/mi-var-invalidate/basics into ../../gdb/gdb (end of file).
> ... and 8 more entries
As you're aware, the above are flaky results that the CI wasn't able to
filter out as it normally does. Sorry for the false positive.
--
Thiago
next prev parent reply other threads:[~2024-01-17 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 19:55 ci_notify
2024-01-17 17:23 ` Thiago Jung Bauermann [this message]
2024-01-18 10:56 ` Nick Clifton
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=87ttnb6fhz.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-testers@sourceware.org \
--cc=linaro-toolchain@lists.linaro.org \
--cc=nickc@redhat.com \
--cc=tcwg-validation@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).