-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update timeout #164
Update timeout #164
Conversation
This reverts commit d8bc532.
WalkthroughThe change updates the Changes
Sequence Diagram(s)sequenceDiagram
participant Test as test_view_raw_ms_data
participant Launch as launch module
Test->>Launch: run(timeout=10)
Launch-->>Test: returns response (or timeout)
Poem
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
test_gui.py (1)
69-69
: Timeout addition looks good.Adding the timeout parameter addresses the failing GUI tests issue mentioned in PR #162, and 10 seconds seems reasonable for viewing raw MS data.
For consistency, consider reviewing other
launch.run()
calls in the file (lines 36, 49, 56, 77, 97, 103) that don't specify timeouts. Adding appropriate timeouts to all run calls would prevent tests from hanging indefinitely.Also, consider extracting timeout values to constants at the top of the file (like
STANDARD_TIMEOUT = 10
andWORKFLOW_TIMEOUT = 60
) for easier maintenance.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
test_gui.py
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: build-full-app
- GitHub Check: build-simple-app
- GitHub Check: build-openms
Thank you for your contribution! LGTM |
Fixes #162
Earlier, the GUI tests were failing because of a timeout issue. I believe this should fix that.
Summary by CodeRabbit