Main
gstack's tests pass on every push to main again, and Windows runs finish in time
Every push to main since 1.91.106.0failed the held-install recovery test
The fixture made a branch named
main in its clonethe push checkout already had oneThe fixture now builds on its own orphan branchgreen on push and on pull requests
MainWindowsTimings
garrytan/gstack · CHANGELOG.md 1.91.118.0
Every push to gstack's main branch had been failing one test, while pull requests passed. The test made a main branch the push checkout already had. It now builds on its own branch.
Windows
The Windows gstack-doctor test stops timing out
Five full doctor passes in one test20 to 30 s against a 30 s limit
Three tests, one per casesame 13 assertions, no timeout raised
The
EBUSY cleanup error after itgone with the timeoutMainWindowsTimings
garrytan/gstack · CHANGELOG.md 1.91.120.0
On Windows, one doctor test ran five full passes against a thirty second limit. It is now three tests with the same thirteen checks. The locked folder error after the timeout is gone too.
Timings
Fresh test timings keep the slow files apart
Windows: gstack-doctor gets a shard of its own, so no shard runs into the 15-minute job limit1.91.121.0
The weekly health check passes its seed check again, with 54 new test files timed1.91.119.0
The recorder honors
--wall-timeout instead of cutting every file at 360 s1.91.121.0CHANGELOG.mdThe “If you…” steps for each fixMainWindowsTimings
garrytan/gstack · CHANGELOG.md 1.91.119.0 · 1.91.121.0
Test timings were recorded fresh, so the slowest Windows file gets its own shard and stays under the fifteen minute limit. The weekly health check passes again. And the recorder stops cutting slow files short.
