public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31351] New: [gdb/testsuite] UNRESOLVED: gdb.dap/ada-nested.exp: compilation prog.adb
Date: Wed, 07 Feb 2024 08:34:45 +0000	[thread overview]
Message-ID: <bug-31351-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31351

            Bug ID: 31351
           Summary: [gdb/testsuite] UNRESOLVED: gdb.dap/ada-nested.exp:
                    compilation prog.adb
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

I ran the following loop:
...
$ for n in $(seq 1 100); do echo $n; ./test.sh 2>&1 | grep "# of " | sort -u;
cp gdb.log gdb.$n.log; done
...
where test.sh runs the dap tests.

I was surprised to see in the results:
...
$ grep UNRESOLVED: gdb.*.log
gdb.11.log:UNRESOLVED: gdb.dap/ada-nested.exp: compilation prog.adb
gdb.29.log:UNRESOLVED: gdb.dap/ada-nested.exp: compilation prog.adb
gdb.37.log:UNRESOLVED: gdb.dap/ada-nested.exp: compilation prog.adb
gdb.72.log:UNRESOLVED: gdb.dap/ada-nested.exp: compilation prog.adb
gdb.78.log:UNRESOLVED: gdb.dap/ada-nested.exp: compilation prog.adb
gdb.79.log:UNRESOLVED: gdb.dap/ada-nested.exp: compilation prog.adb
...

The test run still produces the same amount of passes (minus one for the
compilation), so the compilation actually went fine (otherwise there wouldn't
be any passes).

When issuing a pass for the compilation, dejagnu changes it into an unresolved.

This is a carry-over of the ERROR seen in gdb.dap/pause.exp (see PR31275),
which is run just before.  

It thought we had fixed carrying over things from one test-case to another, but
it seems in this case we still have that problem.

FTR, running test.sh with bash -x gives:
...
+ make V=1 -O check 'RUNTESTFLAGS=gdb.dap/ada-arrays.exp gdb.dap/ada-nested.exp
gdb.dap/ada-scopes.exp gdb.dap/args-env.exp gdb.dap/assign.exp
gdb.dap/attach.exp gdb.dap/basic-dap.exp gdb.dap/bt-nodebug.exp
gdb.dap/catch-exception.exp gdb.dap/children.exp gdb.dap/cond-bp.exp
gdb.dap/cwd.exp gdb.dap/cxx-exception.exp gdb.dap/eof.exp gdb.dap/frameless.exp
gdb.dap/hover.exp gdb.dap/lazy-string.exp gdb.dap/log-message.exp
gdb.dap/memory.exp gdb.dap/modules.exp gdb.dap/pause.exp gdb.dap/ptrref.exp
gdb.dap/remote-dap.exp gdb.dap/rust-slices.exp gdb.dap/scopes.exp
gdb.dap/sources.exp gdb.dap/stack-format.exp gdb.dap/stop-at-main.exp
gdb.dap/terminate.exp gdb.dap/type_check.exp '
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-02-07  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  8:34 vries at gcc dot gnu.org [this message]
2024-02-27  9:07 ` [Bug testsuite/31351] " vries at gcc dot gnu.org
2024-02-27 15:24 ` cvs-commit at gcc dot gnu.org
2024-02-27 15:25 ` vries at gcc dot gnu.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-31351-4717@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: 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).