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
Electron app startup is very slow #11241
Labels
need-to-reproduce
More clues are required to reproduce the issue.
:type/dev
This label is used to indicate that an issue or PR is related to development tasks or changes that
Comments
andelf
added
:type/dev
This label is used to indicate that an issue or PR is related to development tasks or changes that
need-to-reproduce
More clues are required to reproduce the issue.
labels
Apr 18, 2024
Use |
This is the output I get on a 10s timeout:
This is with a
It doesn't seem to give any additional info. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
need-to-reproduce
More clues are required to reproduce the issue.
:type/dev
This label is used to indicate that an issue or PR is related to development tasks or changes that
Search first
What Happened?
When running
yarn e2e-test
, the startup time for the Electron app can be very slow.I have tried to adjust the timeout on the
beforeAll
hook to account for that (ate2e-tests/fixtures.ts:46
, introducingbase.slow()
orbase.setTimeout()
with different values), but even with a 180s timeout, sometimes the timeout gets exceeded:I am currently hunting timeouts that are too short for e2e-tests to run correctly on my config, and this one is the one I have increased the most yet. I could theoretically increase it even further, but at this point I feel like it's a waste of time, and that there's probably a cause to be found somewhere in the code. I don't have any clues though.
Reproduce the Bug
Run e2e tests
Expected Behavior
No response
Screenshots
No response
Desktop or Mobile Platform Information
No response
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: