gstack 1.91.370.0

1.91.370.0
Added 5
  • workflow_dispatch accepts free_runner (ubicloud-standard-2, -4 or -8 only) and free_shards (1–40) for sizing experiments.
  • Runs that override free_runner or free_shards state in their job summary that they are sizing experiments, not PR or train Free Tests results.
  • Every free-suite shard prints RESOURCES with peak_used_mib, min_free_disk_mib and samples from a memory and disk sample every 2 s, even when the suite fails.
  • Tests in test/free-tests-workflow-wiring.test.ts run the real free-plan step with a stubbed bun and check override validation.
  • Tests in test/free-durations-record-workflow.test.ts check that both runners are Ubicloud standard runners.
Changed 3
  • The free suite now runs on ubicloud-standard-2 instead of ubicloud-standard-8 at the same 20 shards, for about a quarter of the runner cost.
  • Free-suite runner and shard count are set by workflow-level FREE_SUITE_RUNNER (ubicloud-standard-2) and FREE_SUITE_SHARDS (20) for pull_request, push and dispatch runs alike.
  • The duration-seed recorder stays on ubicloud-standard-8.

From gstack

The free suite now runs on ubicloud-standard-2 instead of ubicloud-standard-8, at the same 20 shards, for about a quarter of the runner cost. Each shard runs its files one at a time, so it waits on disk and processes rather than CPU. In three paired rounds at one commit, the median per-shard time rose by 3 to 8 s, inside the round-to-round spread, while runner-minutes stayed about equal (464 vs 475). Peak memory stayed under 2.5 GiB and free disk above 15 GiB. A 16-shard arm was slower beyond that spread, so the shard count stays at 20. .github/workflows/free-tests.yml: one workflow-level FREE_SUITE_RUNNER (ubicloud-standard-2) and FREE_SUITE_SHARDS (20) set the free-suite size for pull_request, push and dispatch runs alike. The duration-seed recorder stays on ubicloud-standard-8. Sizing experiments without a workflow edit: workflow_dispatch takes free_runner (ubicloud-standard-2, -4 or -8 only) and free_shards (1–40). A run that overrides either one says in its job summary that it is a sizing experiment, not a PR or train Free Tests result. Every free-suite shard prints RESOURCES: peak_used_mib, min_free_disk_mib and samples from a memory and disk sample every 2 s, even when the suite fails. If a shard shows OOM, ENOSPC or an unexplained Chromium launch failure, move FREE_SUITE_RUNNER to ubicloud-standard-4. Tests in test/free-tests-workflow-wiring.test.ts run the real free-plan step with a stubbed bun and check the override validation; test/free-durations-record-workflow.test.ts checks both runners are Ubicloud standard runners.

View original

Upgraded? How did it go?

Discussion