Skip to content

Increase timeouts for slow steps in CLI regression test - #665

Merged
Martin-Molinero merged 1 commit into
masterfrom
bug-flaky-cli-test-timeouts
Aug 26, 2026
Merged

Increase timeouts for slow steps in CLI regression test#665
Martin-Molinero merged 1 commit into
masterfrom
bug-flaky-cli-test-timeouts

Conversation

@Martin-Molinero

Copy link
Copy Markdown
Member

Summary

  • The Regression Testing workflow fails intermittently in tests/test_cli.py::test_cli with subprocess.TimeoutExpired after 120s, e.g. run 31639781641 on lean report (report container stalled while rendering the rolling beta plot) and nightly runs 32792189159 / 32913644377 on lean cloud backtest (waiting on the cloud queue).
  • These steps depend on the LEAN Docker image and the cloud backtest queue rather than lean-cli code, so raise their timeout to 600s, matching what the test already uses for lean data generate.

Test plan

  • Regression Testing workflow passes on this PR

🤖 Generated with Claude Code

https://claude.ai/code/session_017m9ymW3MmXws555rUWzPyH

The end-to-end CLI test used the default 120s timeout for `lean report`
and `lean cloud backtest`, whose duration depends on the LEAN Docker
image rendering time and the cloud backtest queue. Raise them to 600s,
matching `lean data generate`, to avoid spurious CI failures.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017m9ymW3MmXws555rUWzPyH
@Martin-Molinero
Martin-Molinero merged commit 006af3c into master Aug 26, 2026
70 checks passed
@Martin-Molinero
Martin-Molinero deleted the bug-flaky-cli-test-timeouts branch August 26, 2026 22:33
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