-
Notifications
You must be signed in to change notification settings - Fork 115
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
build: Try in vain to improve CI times #4038
Conversation
Yawning
commented
Jun 16, 2021
•
edited
Loading
edited
- I think using the insecure beacon should be faster in theory, try it
- Seems faster, between 3 to 63 seconds in execution reduction, time to set the option on even more tests.
- Remove/rewrite the rust based runtime tests.
d8c83e6
to
9bbad1d
Compare
Codecov Report
@@ Coverage Diff @@
## master #4038 +/- ##
==========================================
- Coverage 66.78% 66.43% -0.36%
==========================================
Files 391 411 +20
Lines 38138 42317 +4179
==========================================
+ Hits 25472 28115 +2643
- Misses 9017 10232 +1215
- Partials 3649 3970 +321
Continue to review full report at Codecov.
|
2456db8
to
f788ae9
Compare
41eaccd
to
30a5987
Compare
567f0ea
to
3760d80
Compare
7c3f2fa
to
ed4dae8
Compare
This requires #4096, because this PR is the one that found the issue. |
1bdffcb
to
4031355
Compare
27208f0
to
fb86bbc
Compare
This should be faster than using the full PVSS beacon because epoch transitions can happen immediately.
This moves the test client behind an abstract interface (for the most part) so I don't go insane trying to replace every instance of the rust clients.
fb86bbc
to
234e1fe
Compare