-
Notifications
You must be signed in to change notification settings - Fork 126
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
split MG CI jobs #1056
Merged
Merged
split MG CI jobs #1056
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
plebhash
force-pushed
the
split-mg-ci-jobs
branch
from
July 16, 2024 13:20
95b7b3d
to
8a7aa53
Compare
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
plebhash
force-pushed
the
split-mg-ci-jobs
branch
3 times, most recently
from
July 16, 2024 13:33
25f6e3d
to
c68838e
Compare
plebhash
force-pushed
the
split-mg-ci-jobs
branch
3 times, most recently
from
July 16, 2024 14:19
3fb3fdd
to
d85bc50
Compare
plebhash
force-pushed
the
split-mg-ci-jobs
branch
3 times, most recently
from
July 16, 2024 14:50
e2dbc76
to
4113fe6
Compare
this is a paliative solution to stratum-mining#1028 we make MG CI slightly less worse by breaking tests into multiple jobs and allowing us to re-run false alarms in a more agile way MG Tests are also separated from Tarpaulin
plebhash
force-pushed
the
split-mg-ci-jobs
branch
from
July 16, 2024 15:37
4113fe6
to
0c48714
Compare
GitGab19
approved these changes
Jul 17, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is a paliative solution to the issues described on #1028
first, we split the
Coverage
CI into two files:coverage.yaml
: which remains with thetarpaulin
tests, fully focused on code coveragemg.yaml
: which now focuses on Message Generator tests onlywe make MG CI slightly less worse by breaking tests into multiple jobs and allowing us to re-run false alarms in a more agile way
before:
after:
specific MG tests are still subject to false alarms... and when they happen, our only recourse is clicking this button:
but now, instead of re-running the entire MG test stack, we only re-run specific MG tests that failed, which is now possible because they are separate jobs: