-
Notifications
You must be signed in to change notification settings - Fork 208
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: Update/maintain test-install GA workflow #5082
Conversation
3a8eb2f
to
42393d4
Compare
@ltalirz The PR is currently in draft mode, because I have deactivated all unrelated GA runs to save on time and resources. I would appreciate if you could review the PR in draft mode so that all necessary changes and fixes can be implemented in an efficient manner without accidentally merging it. Once the PR is accepted, I will do one final run with all workflows restored before merge. I recommend to not squash this PR on merge. |
@ltalirz Let me know if I can help with the review. |
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.
thanks @csadorf , looks good to me.
My only comment regards the job dependencies: while I get that this makes sense from a perspective of saving resources, does it lead to a slowdown in practice?
I guess the jobs don't actually depend on each other to run successfully but rather if one job fails, then we know that the others will fail as well?
I'm ok with both approaches; just curious to know whether the total runtime differs significantly (maybe the effect is anyhow small).
Yes, the idea was to save some resources, but it is true that some of those jobs do not actually depend on each other in the way that it is configured, but rather belong to a "topical unit". I guess it would be better practice to remove those dependencies and run everything maximal parallel. I will rewire the dependencies and request another review. |
d56ce15
to
6f032d2
Compare
@ltalirz Job dependencies are rewired. The runtime (without actually running the test suite) has been slightly reduced, but I guess this depends on how many workers GitHub makes available to us at a given time. https://github.com/aiidateam/aiida-core/actions/runs/1142730871 |
thanks @csadorf - up to you how to handle the dependency situation, both is fine with me. Feel free to bring back the rest and merge without further review from my side |
This job checks whether the environments defined in the requirements/ files are resolvable.
…ons. Verifies that aiida can be installed with conda for all supported Python versions.
6f032d2
to
e38d636
Compare
Codecov Report
@@ Coverage Diff @@
## develop #5082 +/- ##
========================================
Coverage 80.50% 80.50%
========================================
Files 531 531
Lines 37020 37020
========================================
Hits 29799 29799
Misses 7221 7221
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Related to: #5046 (comment)
Should catch issues with the definition of workflow files in the future.
I have verified that the
resolve-pip-dependencies
job (see below) fails without this change.Checks whether environments defined in the requirements/ files are resolvable.
The test whether we can actually install aiida with
conda install aiida-core ...
is run as a dedicated job only after we checked that we can create a conda environment from theenvironment.yml
file.To test whether
conda install aiida-core ...
actually works for all supported Python versions.Checklist before merge: