Skip to content

fix(livetest): the forfeit step keeps the T bots when it kicks the CT ones - #294

Merged
sivert-io merged 1 commit into
masterfrom
fix/livetest-forfeit-quota
Oct 28, 2026
Merged

sivert-io merged 1 commit into
masterfrom
fix/livetest-forfeit-quota

Conversation

@sivert-io

Copy link
Copy Markdown
Contributor

The live test's forfeit step failed on the 2026-10-28 nightly. That left the compatibility page at "Static check OK, live pending".

  • Cause: the step switches bot_quota_mode to normal with 8 bots on the server and bot_quota 4. In normal mode the quota counts every bot, so CS2 dropped 4 at random. This time it dropped the T bots. The test then kicked the CT bots, and both teams were empty (ct=0+0 t=0+0 in the console capture). With both teams empty there's no single team to forfeit, so no countdown started.
  • Fix: before switching modes, the step sets bot_quota to the number of bots on the server. Kicking the CT bots then refills T (bot_join_team T), and team2 stays present. Cleanup still restores the old quota and mode.
  • Not a Ready Up bug: the 2026-10-27 run passed with the same code, because CS2 happened to drop CT bots.

🤖 Generated with Claude Code

… ones

Switching bot_quota_mode to normal with 8 bots and bot_quota 4 made CS2
drop 4 bots at random. When it dropped the T ones, both teams were empty
and no forfeit started (nightly 2026-10-28). Raise the quota to the bots
there first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sivert-io
sivert-io merged commit bd8b178 into master Oct 28, 2026
4 checks passed
@sivert-io
sivert-io deleted the fix/livetest-forfeit-quota branch October 28, 2026 20:16
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant