rr-debugger / rr-debugger/rr

CI: Intermittent failure in sched_yield test

Open
#3,157 0 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

https://buildkite.com/julialang/rr/builds/288#f90ad74f-115a-4ee1-842d-a46cb07ca9a6



1180/2773 Test  #586: sched_yield .......................................................***Failed  Error regular expression found in output. Regex=[FAILED]  0.47 sec
--
  | source_dir/src/test/util.sh: line 245: 115914 Aborted                 _RR_TRACE_DIR="$workdir" test-monitor $TIMEOUT record.err $RR_EXE $GLOBAL_OPTIONS record $LIB_ARG $RECORD_ARGS "$exe" $exeargs > record.out 2> record.err
  | Test 'sched_yield' FAILED: : token 'EXIT-SUCCESS' not in record.out:
  | --------------------------------------------------
  | FAILED: errno=0 (Success)
  | FAILED: !("ping thread: " && PONG == last)
  | --------------------------------------------------
  | Test sched_yield failed, leaving behind /cache/build/exclusive-amdci3-0/julialang/rr/obj/my_temp_parent_dir/jl_uDNbtn/rr-test-sched_yield-ce1R7Q0DP
  | To replay the failed test, run
  | _RR_TRACE_DIR=/cache/build/exclusive-amdci3-0/julialang/rr/obj/my_temp_parent_dir/jl_uDNbtn/rr-test-sched_yield-ce1R7Q0DP rr replay
  |  

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 the sched_yield test failure in the Buildkite log and source_dir/src/test/util.sh:245. Use the provided RR_TRACE_DIR replay command to inspect the failed trace and determine why EXIT-SUCCESS is missing. Done means the test completes without FAILED output and reliably reports EXIT-SUCCESS.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
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.