-
Couldn't load subscription status.
- Fork 31
Always use --all-combinations and --build on CI
#158
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
|
I dont think its viable to have it this way (25-30 mins of CI runs), probably we should revert this changes and just open an issue when a scheduled CI run fails |
|
How did we go from 5-6 minutes to 25+? 🤔 |
I guess 6 minutes was the time it took to fail. cc @bugadani |
|
No, CI used to finish in 5 minutes (https://github.com/esp-rs/esp-generate/actions/runs/13724008064), I guess caching works differently when it's always working with the main branch. |
|
The bump from 20 minutes to almost 3h was on 7th of March apparently |
|
From these I can only imagine #141 to do something relevant - i.e. sometimes using nightly Thing I don't really understand however: The last build here took 42 minutes while the last successful nightly was 4h and 17 minutes - these is always some randomness is how long it takes but that looks wild |
|
Maybe we should open an issue to investigate this, in the meantime I've created #159 |





No description provided.