Concurrent rr recordings behave worse than serialized ones
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
STR:
- clone https://github.com/servo/servo/
- run
./mach build --release - run
./mach test-wpt --release --chaos --processes 1 tests/wpt/mozilla/tests/mozilla/referrer-policy/no-referrer/http-rp/same-origin/http-http/iframe-tag/ - 3 tests should finish running without incident, then the set of tests will be repeated until an unexpected result is found. Let it run at least once more, then interrupt it.
- run
./mach test-wpt --release --chaos --processes 2 tests/wpt/mozilla/tests/mozilla/referrer-policy/no-referrer/http-rp/same-origin/http-http/iframe-tag/
Expected:
The tests should take less time to run, and no unexpected timeouts should be encountered.
Actual:
▶ TIMEOUT [expected OK] /_mozilla/mozilla/referrer-policy/no-referrer/http-rp/same-origin/http-http/iframe-tag/generic.no-redirect.http.html
│
│ VMware, Inc.
│ Gallium 0.4 on softpipe
└ 3.3 (Core Profile) Mesa 12.0.1
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
Reproduce the issue with ./mach build --release, then run the specified WPT path with --processes 1 and --processes 2 using ./mach test-wpt --release --chaos. Compare runtime and timeout behavior across the serialized and concurrent runs; done means the concurrent run is faster without unexpected timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100