Skip to content
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

bump timeout by one second for windows tests #1159

Closed

Conversation

Atomic-Germ
Copy link
Contributor

@Atomic-Germ Atomic-Germ commented Feb 12, 2025

Related issue

Closes #1158

Context / Background

Currently the Windows mocha tests will fail sometimes, due to a timeout.

What change is being introduced by this PR?

I changed the timeout for that portion from 2 seconds to 3. It doesn't take 3 seconds, but it does take more than 2 in some cases.

How will this be tested?

Applying this PR to a timeout failing branch it should fix that.

Screenshots

Before:
Screenshot 2025-02-12 at 9 34 30 AM

After:
Screenshot 2025-02-12 at 9 29 34 AM

Copy link

codecov bot commented Feb 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

see 1 file with indirect coverage changes

@tupaschoal
Copy link
Collaborator

I'm confused, as the screenshot in the issue you opened shows that what is failing is __tests__\__main__\main-window.mjs:363

@Atomic-Germ
Copy link
Contributor Author

The timeout is the reason it fails.

@@ -202,7 +202,7 @@ describe('Test Workday Waiver Window', function()
beforeEach(async() =>
{
await prepareMockup();
});
}).timeout(3000);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a comment explaining the reason behind the added timeout?
And was the beforeEach() the reason and not really a test?

@tupaschoal
Copy link
Collaborator

The timeout is the reason it fails.

I understand the timeout is the reason, but it is a timeout on __tests__\__main__\main-window.mjs:363, not __tests__/__renderer__/workday-waiver.mjs, no?

@Atomic-Germ
Copy link
Contributor Author

I'm closing this for two reasons, but mainly because I'm not certain why that particular test is the one that made it stop happening and it makes a lot more sense to just run the windows tests with a raised timeout from the script.

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.

Intermittent Windows Mocha Test Failure
3 participants