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
Summary
OrderReporterproduces an emptylog/test_order.logwhen 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