Right now, this repo has three "end-to-end" scripts that run in CI (one for each of the "setup" scripts):
Create: typically around 2-2.5 minutes in total
Initialize: typically around 2-2.5 minutes in total
Migrate: typically around 4-5 minutes in total
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.
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.