CI: rseq-32 test intermittently does not finish
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
E.g. https://buildkite.com/julialang/rr/builds/220#7dd3d2e4-d59f-4d14-a731-24ccf24ff78e
@DilumAluthge On timeout, can we SIGTERM all running processes and collect the TMPDIR, like we do for Julia CI?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the rseq-32 test and the linked Buildkite failure to understand where the intermittent timeout occurs. Compare the timeout behavior with Julia CI, as requested in the issue. Done means timed-out runs SIGTERM all running processes and collect the TMPDIR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100