Skip to content

ci: drop the OS_SANDBOX_HOOK_TIMEOUT_MS=10000 floor — redundant after ADR-0102 D1 #3328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 1 commit into from
Jul 20, 2026
Merged

ci: drop the OS_SANDBOX_HOOK_TIMEOUT_MS=10000 floor — redundant after ADR-0102 D1 #3328

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,17 +15,6 @@ concurrency:
group: ci-${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true

# The QuickJS sandbox compiles a fresh WASM module per hook/action invocation
# (and a nested hook compiles another inside the parent's budget). Hosted runners
# are 4-vCPU and the test job oversubscribes them (`turbo --concurrency=4` + each
# vitest worker), so that fixed VM-creation cost alone intermittently tripped the
# 250ms hook default even while the VM was progressing — a load flake unrelated to
# the change under test (#3259). Raise the sandbox hook budget for the whole
# workflow; production keeps the 250ms default (this only sets it in CI). Real
# hangs are still bounded by each test's own vitest timeout.
env:
OS_SANDBOX_HOOK_TIMEOUT_MS: '10000'

jobs:
filter:
runs-on: ubuntu-latest
Expand Down