- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 81
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
🛠 Tooling: Investigate performance improvements for end-to-end scripts in CI #860
Closed
3 tasks done
Labels
area: tooling
Managing the repository's maintenance
status: blocked
Waiting for something else to be resolved
Comments
This was referenced Dec 30, 2023
3 tasks
As of #1610 (and before it, even), things are down to 1-1.5 minutes. Progress! |
2 tasks
I put some logs in migration:
Interesting that
|
This will likely be superceded by #1782. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: tooling
Managing the repository's maintenance
status: blocked
Waiting for something else to be resolved
Bug Report Checklist
main
branch of the repository.Overview
Right now, this repo has three "end-to-end" scripts that run in CI (one for each of the "setup" scripts):
5 minutes in CI is way too long for a terminal app like this! Especially since test coverage merges in coverage results from all those scripts.
Can they be sped up? Is there any caching that can be done, maybe? Or is there a slowdown in a dependency that can be resolved?
Additional Info
I suspect that reducing log spam will help with this issue a lot: #859. Even if the log spam isn't hurting performance, reducing spam will likely make investigating easier.
The text was updated successfully, but these errors were encountered: