Skip to content

fix(ci): gave the unit tests 120 seconds to finish in CI instead of 60 - #343

Merged
FlareCoding merged 1 commit into
masterfrom
pr/ci-test-timeout
Oct 6, 2026
Merged

FlareCoding merged 1 commit into
masterfrom
pr/ci-test-timeout

Conversation

@FlareCoding

@FlareCoding FlareCoding commented Oct 6, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • The aarch64 unit tests run under emulation on GitHub's runners and recently took between 27 and 63 seconds, so a slow runner could hit the 60 second limit with every test passing.
  • CI gives the test run 120 seconds, and local runs keep the 60 second default.

Note

Low Risk
CI-only workflow env change; no production or test logic changes beyond allowing longer QEMU runs.

Overview
CI kernel unit-tests now set STLX_TEST_TIMEOUT=120 on the make test step so QEMU runs get 120 seconds instead of the harness default of 60 (scripts/run_tests.sh uses STLX_TEST_TIMEOUT with a 60s fallback).

This targets flaky CI failures on slow runners—especially aarch64 under emulation, where recent runs were already near the old limit while tests still passed. Local make test behavior is unchanged when the env var is unset.

Reviewed by Cursor Bugbot for commit d715c9b. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-authored-by: Cursor <cursoragent@cursor.com>
@FlareCoding
FlareCoding merged commit 4eddbe8 into master Oct 6, 2026
15 checks passed
@FlareCoding
FlareCoding deleted the pr/ci-test-timeout branch October 6, 2026 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant