Repository navigation
Commit 385d9ea
committed
chore(spec): per-test wall-clock timing + documentation reporter
The default rspec progress (dots) hides which test is in flight when a
runner stalls. Last week's CI on Ruby 3.4 spent 41 minutes silently
between two examples — the log only shows DEPRECATION warnings before
and after, so the culprit was unidentifiable.
Adds .rspec config (--format documentation, --profile 25) and a
support/timing.rb hook that warns:
[timing] start <full description>
[timing] N.NN s <pass|fail> <full description>
on each example. Two effects:
* A hung runner now leaves a 'start ...' breadcrumb so the next person
knows exactly which spec was mid-flight.
* End-of-run --profile output lists the 25 slowest, which surfaces the
flake culprits without having to scan the whole transcript.1 parent 0d2214b commit 385d9ea
2 files changed
Lines changed: 33 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
0 commit comments