fix(ci): add pytest-timeout to dev deps so nightly stops failing daily#477
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds ChangesDev Dependency & Test Setup
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Warning Review ran into problems🔥 ProblemsStopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds the missing pytest-timeout pytest plugin to the project’s dev optional dependencies so CI workflows that invoke pytest --timeout=... (notably the nightly live integration tests) no longer fail at argument parsing.
Changes:
- Add
pytest-timeoutto[project.optional-dependencies].devinpyproject.toml.
|
@copilot please address the blocking signals on this PR and push a fix commit. Trigger: ci-failure Follow the PR's |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e2e569b485
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Addressed the uv.lock review feedback in commit 51fdf6c — ran |
|
Actionable comments posted: 0 |
Summary
The Nightly — Live Integration Tests workflow has been failing every single night because
pytest --timeout=60errors withunrecognized arguments: --timeout=60— thepytest-timeoutplugin was never added to the[dev]extras. This adds it.Root cause
.github/workflows/nightly.yml:33invokes:pytest tests/integration/test_free_channels_live.py -m "live and not flaky_live" -v --timeout=60 --ignore=tests/perf -x--timeout=Nis provided by thepytest-timeoutplugin.pyproject.toml[project.optional-dependencies].devlisted onlypytest,pytest-asyncio,ruff— nopytest-timeout. Pytest exits with code 4 before collecting any test.Recent failed runs all show the same error (e.g. run
26551922195,26488064725,26429718183— every day this week).Fix
Single-line addition to
[dev]extras:pytest-timeout.Verification
Local repro with the same venv setup as CI:
No more
unrecognized argumentserror.Test plan
Note on push
Pushed with
--no-verify(user-approved) because pre-push runs the full unit suite and a pre-existing flaky test (test_clarify::test_clarifier_returns_question_for_ambiguous_query) fails when run as part of the full suite due to astructlog/stderr capture interaction. It reproduces onorigin/mainindependently of this change. Tracked separately.Summary by CodeRabbit