[Bug testsuite/30567] New: [gdb/testsuite] FAIL: gdb.perf/gmonster1-null-lookup.exp: run

[Bug testsuite/30567] New: [gdb/testsuite] FAIL: gdb.perf/gmonster1-null-lookup.exp: run

[vries at gcc dot gnu.org]

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

            Bug ID: 30567
           Summary: [gdb/testsuite] FAIL:
                    gdb.perf/gmonster1-null-lookup.exp: run
           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: ---

Running check-perf with the default GDB_PERFTEST_MODE=both works fine:
...
$ make check-perf GDB_PERFTEST_MODE=both
  ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/backtrace.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/disassemble.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-null-lookup.exp
...
Running
/data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-pervasive-typedef.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-print-cerr.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-ptype-string.exp
...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-runto-main.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-select-file.exp
...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-null-lookup.exp
...
Running
/data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-pervasive-typedef.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-print-cerr.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-ptype-string.exp
...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-runto-main.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-select-file.exp
...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/single-step.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/skip-command.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/skip-prologue.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/solib.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/template-breakpoints.exp ...

                === gdb Summary ===

# of expected passes            20085
...

But also compile and run are advertised in gdb/testsuite/README.

So, since both implies compile, let's try run:
...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-null-lookup.exp
...
FAIL: gdb.perf/gmonster1-null-lookup.exp: run
DUPLICATE: gdb.perf/gmonster1-null-lookup.exp: run
Running
/data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-pervasive-typedef.exp ...
FAIL: gdb.perf/gmonster1-pervasive-typedef.exp: run
DUPLICATE: gdb.perf/gmonster1-pervasive-typedef.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-print-cerr.exp ...
FAIL: gdb.perf/gmonster1-print-cerr.exp: run
DUPLICATE: gdb.perf/gmonster1-print-cerr.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-ptype-string.exp
...
FAIL: gdb.perf/gmonster1-ptype-string.exp: run
DUPLICATE: gdb.perf/gmonster1-ptype-string.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-runto-main.exp ...
FAIL: gdb.perf/gmonster1-runto-main.exp: run
DUPLICATE: gdb.perf/gmonster1-runto-main.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1-select-file.exp
...
FAIL: gdb.perf/gmonster1-select-file.exp: run
DUPLICATE: gdb.perf/gmonster1-select-file.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster1.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-null-lookup.exp
...
FAIL: gdb.perf/gmonster2-null-lookup.exp: run
DUPLICATE: gdb.perf/gmonster2-null-lookup.exp: run
Running
/data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-pervasive-typedef.exp ...
FAIL: gdb.perf/gmonster2-pervasive-typedef.exp: run
DUPLICATE: gdb.perf/gmonster2-pervasive-typedef.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-print-cerr.exp ...
FAIL: gdb.perf/gmonster2-print-cerr.exp: run
DUPLICATE: gdb.perf/gmonster2-print-cerr.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-ptype-string.exp
...
FAIL: gdb.perf/gmonster2-ptype-string.exp: run
DUPLICATE: gdb.perf/gmonster2-ptype-string.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-runto-main.exp ...
FAIL: gdb.perf/gmonster2-runto-main.exp: run
DUPLICATE: gdb.perf/gmonster2-runto-main.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2-select-file.exp
...
FAIL: gdb.perf/gmonster2-select-file.exp: run
DUPLICATE: gdb.perf/gmonster2-select-file.exp: run
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/gmonster2.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/single-step.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/skip-command.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/skip-prologue.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/solib.exp ...
Running /data/vries/gdb/src/gdb/testsuite/gdb.perf/template-breakpoints.exp ...

                === gdb Summary ===

# of expected passes            20133
# of unexpected failures        12
# of duplicate test names       12
...

Same results if we first do compile and then run.

Looking at the first fail in more detail:
...
(gdb) PASS: gdb.perf/gmonster1-null-lookup.exp: setup perftest: python exec
(open ('${srcdir}/gdb.perf/gmonster-null-lookup.py').read ())
PerfTest::assemble, run ...
python NullLookup('gmonster1:gmonster-null-lookup', ("1-cu", "10-cus",
"100-cus"),
'/data/vries/gdb/leap-15-4/build/gdb/testsuite/gdb.perf/outputs/gmonster1/gmonster1').run()^M
Selecting file
/data/vries/gdb/leap-15-4/build/gdb/testsuite/gdb.perf/outputs/gmonster1/gmonster1-1-cu^M
Traceback (most recent call last):^M
  File "<string>", line 1, in <module>^M
  File "/data/vries/gdb/src/gdb/testsuite/gdb.perf/lib/perftest/perftest.py",
line 66, in run^M
    self.execute_test()^M
  File "<string>", line 38, in execute_test^M
  File "/data/vries/gdb/src/gdb/testsuite/gdb.perf/lib/perftest/utils.py", line
45, in select_file^M
    gdb.execute("file %s" % (file_name))^M
gdb.error:
/data/vries/gdb/leap-15-4/build/gdb/testsuite/gdb.perf/outputs/gmonster1/gmonster1-1-cu:
No such file or directory.^M
Error while executing Python code.^M
(gdb) FAIL: gdb.perf/gmonster1-null-lookup.exp: run
PerfTest::assemble, run complete.
GenPerfTest::run, done Tue Jun 20 11:48:16 2023
PASS: gdb.perf/gmonster1-null-lookup.exp: run
DUPLICATE: gdb.perf/gmonster1-null-lookup.exp: run
...

After reading here ( https://sourceware.org/gdb/wiki/GDBPerfTestsuite ) in the
wiki I'm starting to realize that there are two classes of performance tests,
the monster and non-monster ones, which are run in different ways, which makes
it somewhat problematic that they're in same directory.

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

[Bug testsuite/30567] [gdb/testsuite] FAIL: gdb.perf/gmonster1-null-lookup.exp: run

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> Running check-perf with the default GDB_PERFTEST_MODE=both works fine:

Well, sort of.

The monster tests produce:
...
                verbose -log "Test must be compiled/run in separate steps."
...
so it outright refuses to run "both".

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