-
Notifications
You must be signed in to change notification settings - Fork 58
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
ci: 💚 Reduce self-hosted runner usage #869
base: master
Are you sure you want to change the base?
Conversation
Coverage Report@@ Coverage Diff @@
## master ci/distribute-runners +/- ##
=========================================================
+ Coverage 65.51% 65.97% +0.46%
- Files 343 339 -4
- Lines 59504 59084 -420
=========================================================
- Hits 38982 38978 -4
- Misses 20522 20106 -416
|
WASM runtime size check:Compared to target branchdancebox runtime: 1416 KB (no changes) ✅ flashbox runtime: 824 KB (no changes) ✅ dancelight runtime: 2172 KB (+2172 KB) container chain template simple runtime: 1116 KB (-4304 KB) ✅ container chain template frontier runtime: 1404 KB (-5156 KB) ✅ |
@timbrinded if nextest is giving problems, can you split that into a future PR? The other changes are already very valuable, I don't want to be blocked by that |
I'm very close, let me cook @tmpolaczyk |
Changes
SplitOur runners have too slow network speed so do not benefit from shardingrust-test
into generating the test files and then execution step.Context
The queue to use
self-hosted
runners can sometimes be over an hour long.This has introduced a blockages into the critical path, which can be ameliorated by lowering the usage of self-hosted for heavy tasks only.