Skip to content

test(scripts): raise ExecuteFlow timeout to fix cold-start flakes#393

Merged
jymaire merged 1 commit into
mainfrom
fix/go-runner-test-timeout
Jul 6, 2026
Merged

test(scripts): raise ExecuteFlow timeout to fix cold-start flakes#393
jymaire merged 1 commit into
mainfrom
fix/go-runner-test-timeout

Conversation

@jymaire

@jymaire jymaire commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

What

Raise the @ExecuteFlow await timeout from the default 60s to PT5M on the heavier script runner tests: go, dotnet, deno, bun, php.

Why

The main check failed on run 28774084040:

> Task :plugin-script-go:test FAILED
org.junit.jupiter.api.extension.ParameterResolutionException:
  Execution 9AfwddQhvsAl8RiFCiQW6 is currently at the status RUNNING which is not the awaited one

@ExecuteFlow's parameter resolver awaits the execution reaching a terminal state, with a default timeout of 60s (PT60S). The all_*.yaml sanity-check flows run script tasks that compile/build inside a Docker task runner (Go's all_go.yaml runs two go run tasks that each compile). On a cold CI runner, image pull plus compilation exceeded 60s, so the execution was still RUNNING at the deadline — a cold-start flake, not a regression.

Fix

@ExecuteFlow(value = "sanity-checks/all_<lang>.yaml", timeout = "PT5M")

Applied to the runner tests most exposed to cold-start latency. Gives comfortable headroom for image pull + compilation while still failing fast on a genuine hang. All four modules compile (compileTestJava); go verified previously.

jbang, julia, and r don't use @ExecuteFlow, so they're unaffected.

🤖 Generated with Claude Code

@jymaire jymaire self-assigned this Jul 6, 2026
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

📦 Artifacts

Name Size Updated Expiration
jar 56.71 MB Jul 6, 26, 7:51:21 AM UTC Jul 13, 26, 7:51:19 AM UTC

🧪 Java Unit Tests

TestsPassed ✅SkippedFailedTime ⏱
Java Tests Report238 ran238 ✅0 ⚠️0 ❌26m 18s 129ms

🔁 Unreleased Commits

✅ No unreleased commits found.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Tests report quick summary:

success ✅ > tests: 238, success: 238, skipped: 0, failed: 0

unfold for details
Project Status Success Skipped Failed
plugin-script-bun success ✅ 3 0 0
plugin-script-deno success ✅ 3 0 0
plugin-script-dotnet success ✅ 8 0 0
plugin-script-go success ✅ 18 0 0
plugin-script-groovy success ✅ 8 0 0
plugin-script-jbang success ✅ 2 0 0
plugin-script-julia success ✅ 2 0 0
plugin-script-jython success ✅ 5 0 0
plugin-script-lua success ✅ 3 0 0
plugin-script-nashorn success ✅ 6 0 0
plugin-script-node success ✅ 13 0 0
plugin-script-perl success ✅ 3 0 0
plugin-script-php success ✅ 3 0 0
plugin-script-powershell success ✅ 4 0 0
plugin-script-python success ✅ 69 0 0
plugin-script-r success ✅ 2 0 0
plugin-script-ruby success ✅ 39 0 0
plugin-script-shell success ✅ 47 0 0

The @ExecuteFlow await defaults to 60s. The all_*.yaml sanity-check
flows run script tasks that compile/build inside Docker; on a cold CI
runner, image pull plus compilation can exceed 60s, leaving the
execution RUNNING at the deadline and failing parameter resolution
(seen on plugin-script-go). Bump the timeout to PT5M on the heavier
runner tests (go, dotnet, deno, bun, php) for headroom while still
failing fast on a genuine hang.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jymaire jymaire force-pushed the fix/go-runner-test-timeout branch from 108889d to 31b8ef0 Compare July 6, 2026 07:45
@jymaire jymaire changed the title test(go): raise all_go ExecuteFlow timeout to fix cold-start flake test(scripts): raise ExecuteFlow timeout to fix cold-start flakes Jul 6, 2026
@jymaire jymaire requested review from Malaydewangan09 and fdelbrayelle and removed request for fdelbrayelle July 6, 2026 07:48
@jymaire jymaire merged commit a2e3d27 into main Jul 6, 2026
9 checks passed
@jymaire jymaire deleted the fix/go-runner-test-timeout branch July 6, 2026 08:20
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.

2 participants