gstack 1.91.166.0 stops the Windows setup and display tests failing under load

53 minutes ago

gstack 1.91.166.0 fixes two of its own tests that failed under load: the Windows setup test now warms up PowerShell 5.1 before the cold-start case, and the virtual display test moves to its own display range. gstack runs the same after upgrading. Release notes, 1.91.166.0: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911660---2026-10-20 Commits: https://github.com/garrytan/gstack/commits/main

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00Windows setup
  2. 0:14Display test
  3. 0:29Your setup
Show transcript

Windows setup

gstack logo

gstack 1.91.166.0 warms up PowerShell 5.1 before the Windows setup test

first launch max 5.04 s
bun test limit 5 s
beforeAll launches PowerShell 5.1 once, so no test pays the cold start
Windows setupDisplay testYour setup
garrytan/gstack · CHANGELOG.md · 1.91.166.0

gstack's Windows setup test failed on cold starts. The first PowerShell 5.1 launch can take over five seconds, past the test's limit. A warm-up launch now runs first, and no timeout changed.

Display test

The virtual display test now picks from a range of its own

before:99–:110now:25000–:25100
30 of 30 runs pass under the same parallel load
No free display now fails the test instead of passing quietly
Windows setupDisplay testYour setup
garrytan/gstack · CHANGELOG.md · 1.91.166.0

The virtual display test shared display numbers with headed browsers in parallel shards, and collided in up to nine of twenty runs. On a private range, it passes every run.

Your setup

gstack runs the same for you; its own checks go red less often

CHANGELOG.md1.91.166.0 · Fixed
Do you run gstack on Windows, a Mac or Linux?
Windows setupDisplay testYour setup
garrytan/gstack · CHANGELOG.md · 1.91.166.0

Both fixes are in gstack's own tests, so it runs the same for you, with fewer red checks. Details are in the changelog. Do you run gstack on Windows, a Mac or Linux?