public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug rust/26197] rust FAILs with rustc 1.36.0 and llvm 7 Date: Thu, 13 Aug 2020 12:43:54 +0000 [thread overview] Message-ID: <bug-26197-4717-PnCim8Bn2C@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26197-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26197 --- Comment #20 from Tom Tromey <tromey at sourceware dot org> --- Ok, I see. The test accepts the bug: set xfail_pattern " = <error reading variable>" gdb_test_multiple "print str_some" "" { -re "\[\r\n\]*(?:$pass_pattern)\[\r\n\]+$gdb_prompt $" { pass $gdb_test_name } -re "\[\r\n\]*(?:$xfail_pattern)\[\r\n\]+$gdb_prompt $" { xfail $gdb_test_name } } I suppose we could just update the xfail pattern then. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-13 12:43 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-02 15:01 [Bug rust/26197] New: " vries at gcc dot gnu.org 2020-07-02 15:01 ` [Bug rust/26197] " vries at gcc dot gnu.org 2020-07-02 15:02 ` vries at gcc dot gnu.org 2020-07-02 15:02 ` vries at gcc dot gnu.org 2020-07-02 15:02 ` vries at gcc dot gnu.org 2020-07-06 9:28 ` vries at gcc dot gnu.org 2020-07-12 21:20 ` tromey at sourceware dot org 2020-07-12 21:35 ` tromey at sourceware dot org 2020-07-13 9:25 ` vries at gcc dot gnu.org 2020-07-13 9:31 ` vries at gcc dot gnu.org 2020-07-14 1:52 ` tromey at sourceware dot org 2020-07-21 20:39 ` tromey at sourceware dot org 2020-07-22 12:55 ` brobecker at gnat dot com 2020-07-22 19:37 ` tromey at sourceware dot org 2020-07-22 19:40 ` tromey at sourceware dot org 2020-07-22 20:02 ` tromey at sourceware dot org 2020-07-22 20:13 ` tromey at sourceware dot org 2020-08-05 16:11 ` cvs-commit at gcc dot gnu.org 2020-08-05 17:52 ` tromey at sourceware dot org 2020-08-05 19:34 ` vries at gcc dot gnu.org 2020-08-12 21:31 ` tromey at sourceware dot org 2020-08-13 11:26 ` vries at gcc dot gnu.org 2020-08-13 12:43 ` tromey at sourceware dot org [this message] 2020-08-13 12:46 ` vries at gcc dot gnu.org 2020-08-13 14:13 ` tromey at sourceware dot org 2020-08-15 6:10 ` vries at gcc dot gnu.org 2020-08-17 16:49 ` cvs-commit at gcc dot gnu.org 2020-08-17 17:04 ` tromey at sourceware dot org 2020-08-17 17:09 ` tromey at sourceware dot org 2020-08-18 9:02 ` vries at gcc dot gnu.org 2020-08-18 9:34 ` vries at gcc dot gnu.org 2020-09-08 16:42 ` tromey at sourceware dot org 2020-09-10 18:39 ` tromey at sourceware dot org 2020-09-10 18:43 ` tromey at sourceware dot org 2020-09-15 15:27 ` cvs-commit at gcc dot gnu.org 2020-09-15 15:48 ` cvs-commit at gcc dot gnu.org 2020-09-15 15:48 ` tromey at sourceware dot org
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=bug-26197-4717-PnCim8Bn2C@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).