Repository navigation
Commit c48392e
committed
Pin the Windows suite to the pack's Node 24.18.0 and keep the raw output of a test file that exits without a failing assertion
Node 24.19.0 and later abort when a better-sqlite3 build made against their headers collects a prepared statement (nodejs/node#65446), which ended eleven test files with exit code 134 after every test had passed. The Windows runtime pack is built with Node 24.18.0, so the suite now runs on that version. A file that exits non-zero with no failing assertion now records the end of its output so the cause is visible.1 parent 705e1bf commit c48392e
2 files changed
Lines changed: 4 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
| 82 | + | |
| 83 | + | |
82 | 84 | | |
83 | 85 | | |
84 | 86 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
41 | 41 | | |
42 | 42 | | |
43 | 43 | | |
44 | | - | |
| 44 | + | |
| 45 | + | |
45 | 46 | | |
46 | 47 | | |
47 | 48 | | |
| |||
0 commit comments