-
Notifications
You must be signed in to change notification settings - Fork 157
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: Decouple LCG and Ubuntu builds #1222
ci: Decouple LCG and Ubuntu builds #1222
Conversation
/cc @stephenswat |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I can tell this is a great way to split up the existing job into four parts, looks great!
Codecov Report
@@ Coverage Diff @@
## main #1222 +/- ##
=======================================
Coverage 47.94% 47.94%
=======================================
Files 373 373
Lines 19495 19495
Branches 9152 9152
=======================================
Hits 9347 9347
Misses 3817 3817
Partials 6331 6331 📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
Hmm, so it looks like the CI is still trying to run the old jobs, which it now no longer has the configuration for anymore? Or how does that work? |
"Required checks" in the PR UI is a UI thing, that's not defined by the job description. I'll have to override this and change the settings if we merge this. |
Ah, that seems... Confusing on Github's part. 🤔 |
Ok, fixed conflicts. Can we go again @stephenswat ? |
Based on acts-project#1222 With acts-project#1222 in, we can have the python level tests and the perf monitoring fail independently of one another. This PR enables that again. Also bumps `histcmp` to v0.4.0 for a fix for missing legends in some plots, and to include standalone PDFs in addition to the HTML report.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approving.
Ok, required old checks are still listed, new ones have passed. Overriding check requirement to merge this then. |
This allows getting rid of some
if/else
branching between these, and allows splitting up the follow up checks (examples+pytest and phys monitoring) into separate jobs that depend on the build job result. This means they can run independently of each other and if either fails, the other will still run and provide output.