-
Notifications
You must be signed in to change notification settings - Fork 32
🐛Increase node testing timeout to wait for website since Github machines are very weak #7893
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
Conversation
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.
Pull Request Overview
This PR increases the waiting timeout in the end-to-end startup test to accommodate slower performance on GitHub's machines.
- Increases the timeout from 10 seconds to 60 seconds.
Comments suppressed due to low confidence (1)
tests/e2e/tests/startupCalls.js:50
- [nitpick] Consider adding a brief comment explaining why the timeout was increased to 60000ms (e.g., to accommodate GitHub machine performance).
await page.waitFor(60000);
|
@mergify queue |
d51539a to
2d9027f
Compare
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at d0e305f |
|
|
Thanks for the effort 👍 Since I see that somehow the playwright test is more reliable, I might move this test there and remove this one. |



What do these changes do?
Increased the time waiting for the website to come up. Since it is slow and the machines testing are weak.
now waits 1 minute instead of 10 seconds, which already on my own computer would not be enough.
These tests are impossible to test locally for me. I am tempted to move all this to playwright. or ditch them if it has no value.
Related issue/s
How to test
Dev-ops