OrderReporter produces empty test_order.log in parallel DRb mode
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 239
- Forks
- 36
- Avg merge
- 28m
- Merged PRs (30d)
- 3
Description
Summary
OrderReporter produces an empty log/test_order.log when tests run in parallel using Rails' ActiveSupport::Testing::Parallelization (forked processes with DRb). This makes it impossible to reproduce order-dependent flaky test failures because the test order is never recorded.
Expected behavior
The test order should be recorded even in parallel DRb mode. Ideally as per-worker files, since a single interleaved file doesn't represent any process's actual execution order and can't be used to bisect state pollution between tests.
Environment
- ci-queue 0.85.0
- Rails with parallelize(workers: N, with: :processes)
- minitest 5.27.0
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the empty log with Rails ActiveSupport::Testing::Parallelization using forked workers and DRb, then trace how OrderReporter records test order. The issue is done when parallel DRb runs preserve usable order data, ideally in per-worker files rather than one interleaved log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100