You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0f7a10a
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: ruby/README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,16 @@ minitest-queue --queue redis://example.com run -Itest test/**/*_test.rb
38
38
39
39
Additionally you can configure the requeue settings (see main README) with `--max-requeues` and `--requeue-tolerance`.
40
40
41
+
To reconstruct process-local artifacts after a distributed worker is retried, replay every test represented by that worker's reservation history:
42
+
43
+
```bash
44
+
minitest-queue --queue redis://example.com \
45
+
--retry-selection worker-history \
46
+
run -Itest test/**/*_test.rb
47
+
```
48
+
49
+
Worker-history retries require the retry to retain its worker ID and queue build ID. Missing reservation history or suite chunk metadata fails the retry. The replay uses a local retry queue and does not rejoin the shared queue, so surviving workers must drain any remaining work. When centralized reporting is used, restarting every worker before the shared queue is exhausted fails the build rather than accepting an incomplete run.
50
+
41
51
42
52
If you'd like to centralize the error reporting you can do so with:
0 commit comments