opensource/kilocode
3
0
Fork 0
mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-08-28 19:11:03 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(ci): apply the 600s per-file kill deadline on every OS

Browse Source 
The deadline exists to catch hangs, not to cap healthy runs. A
saturated Linux shard held cli/run/run-process past 300s with every
test inside passing, and the runner killed it twice. Windows already
ran with 600s for the same reason.
This commit is contained in:
Yury Zialionka
2026-08-13 19:58:53 -06:00
parent b18f2e2f4f
commit 348f90cb9e
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/test.yml
+4 -1
View File
@@ -204,7 +204,10 @@ jobs:
# files run ~230-270s serially there (vs ~40s on macOS/Linux), leaving only ~30s under
# the 300s default; 600s gives healthy-but-slow files real margin without masking hangs
# elsewhere (Linux/macOS keep the 300s default).
KILO_TEST_FILE_TIMEOUT: ${{ matrix.settings.os == 'windows' && '600000' || '' }}
# kilocode_change - 600s on every OS: the deadline guards against hangs, and a
# saturated shard can legitimately hold a heavy real-subprocess file past 300s
# (seen on Linux: run-process passing every test, killed at the deadline twice).
KILO_TEST_FILE_TIMEOUT: "600000"
# kilocode_change end
# kilocode_change start