rr-debugger / rr-debugger/rr

20 tests failing on 5.7.0: vsyscall_reverse_next and so on

Open
#3,631 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.7k
Forks
662
Avg merge
2d 3h
Merged PRs (30d)
2

Description

On bare metal Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz with Linux kernel v6.5.7 there are 20 test failures:

0% tests passed, 20 tests failed out of 20

Total Test time (real) = 2759.49 sec

The following tests FAILED:
        1236 - vsyscall_reverse_next (Failed)
        1237 - vsyscall_reverse_next-no-syscallbuf (Failed)
        1242 - watchpoint_at_sched (Failed)
        1243 - watchpoint_at_sched-no-syscallbuf (Failed)
        1244 - watchpoint_before_signal (Failed)
        1245 - watchpoint_before_signal-no-syscallbuf (Failed)
        1370 - replay_serve_files (Failed)
        1371 - replay_serve_files-no-syscallbuf (Failed)
        1392 - reverse_step_signal (Failed)
        1393 - reverse_step_signal-no-syscallbuf (Failed)
        1396 - reverse_watchpoint (Failed)
        1397 - reverse_watchpoint-no-syscallbuf (Failed)
        1430 - step_signal (Failed)
        1431 - step_signal-no-syscallbuf (Failed)
        1442 - tick0 (Failed)
        1443 - tick0-no-syscallbuf (Failed)
        1444 - tick0_less (Failed)
        1445 - tick0_less-no-syscallbuf (Failed)
        1470 - watchpoint_unaligned2 (Failed)
        1471 - watchpoint_unaligned2-no-syscallbuf (Failed)
Errors while running CTest
Output from these tests are in: /usr/lib64/rr/testsuite/obj/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.

I run ctest -VV -vv first and then ctest --rerun-failed -VV -vv as requested in #3625.
Generated LastTest.log is there LastTest.9.log

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with LastTest.9.log and rerun the listed failures using ctest --rerun-failed -VV -vv in the rr test build. Compare the paired syscallbuf and non-syscallbuf cases, beginning with the first failing test, vsyscall_reverse_next. Done means identifying the common cause and restoring the affected tests on the reported Linux kernel and CPU.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
devtools, operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.