row224: trim whitespace in plain-text failure receipt
This commit is contained in:
1 parent
532938beeb
commit
ed985c0442
1 file changed
+6
-2
@@ -300,10 +300,10 @@ test at packages/cli/tests/thread-launch.test.mjs:216:1
|
|||||||
✖ REQ-THREAD-2 REQ-LAUNCH-1 a running thread counts against its model's limit and an idle-stopped one doesn't (185.485131ms)
|
✖ REQ-THREAD-2 REQ-LAUNCH-1 a running thread counts against its model's limit and an idle-stopped one doesn't (185.485131ms)
|
||||||
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
|
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
|
||||||
+ actual - expected
|
+ actual - expected
|
||||||
|
|
||||||
+ 'harness-binary-missing'
|
+ 'harness-binary-missing'
|
||||||
- 'capacity-full'
|
- 'capacity-full'
|
||||||
|
|
||||||
at TestContext.<anonymous> (file:///mnt/storage/scratch/della-row224-r2/packages/cli/tests/thread-launch.test.mjs:227:10)
|
at TestContext.<anonymous> (file:///mnt/storage/scratch/della-row224-r2/packages/cli/tests/thread-launch.test.mjs:227:10)
|
||||||
at async Test.run (node:internal/test_runner/test:1409:7)
|
at async Test.run (node:internal/test_runner/test:1409:7)
|
||||||
at async Test.processPendingSubtests (node:internal/test_runner/test:974:7) {
|
at async Test.processPendingSubtests (node:internal/test_runner/test:974:7) {
|
||||||
@@ -327,3 +327,7 @@ test at packages/cli/tests/thread-launch.test.mjs:1:1
|
|||||||
✖ packages/cli/tests/thread-launch.test.mjs (62982.9717ms)
|
✖ packages/cli/tests/thread-launch.test.mjs (62982.9717ms)
|
||||||
'Promise resolution is still pending but the event loop has already resolved'
|
'Promise resolution is still pending but the event loop has already resolved'
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Receipt correction: copied test output contained two whitespace-only lines;
|
||||||
|
complete-range diff-check caught them. Trimmed those log lines in this
|
||||||
|
follow-up; no test/code or failure text changed, and no test was rerun.
|
||||||
Reference in new issue
Block a user