-
Notifications
You must be signed in to change notification settings - Fork 4
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 ci.yml
into separate actions
#280
Conversation
Split the "unit-tests" action into multiple actions, currently one for each package contained within the `flepiMoP` repo. Also updated checkout from v3 to v4 to address node16 deprecation warnings and swapped ubuntu 20.04 for ubuntu latest. Changed the gempyor ci to not print stdout and exit on first failure.
That did not do quite what I expected. Let me make a few small edits before this is ready for review. |
Typo in `setwd` call causes error about not being able to change to directory that doesn't exist.
Set the shell to bash so the `source` function is available.
Add the same path related limits from the on push to on pull_requests as well.
These changes are now ready for 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.
Seems conceptually fine, but I'm not expert enough on GH actions syntax.
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.
these look good. one minor thing to fix is to remove breaking-improvements
branch as i believe that is gone. Are there other branches that should be included?
Removed the `breaking-improvements` branch from special consideration in GitHub actions.
Ah, I did not realize that we had sunsetted the |
Look good to me, thanks. As mentionned, perhaps the verbosity and all tests with failure were useful as I know from the commit log we have folks using ci as way to test code. But I agree it's better to not have them in Github action, and we can add it back. the splitting is very welcome. |
Minor edits to run the gempyor tests with python 3.10 and 3.11. Remove usage of custom docker container.
Very minor edit to `__init__.py` to trigger the `gempyor` CI GitHub action.
Need to install `test` extra installs to get pytest instead of `dev`.
This PR is ready for review again. This PR now:
Some open questions:
Steps after this PR:
|
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.
Looks good; one weird space diff, but that's likely test cruft?
@@ -28,6 +28,7 @@ cum_death_forecast <- function (sim_data, | |||
|
|||
} | |||
|
|||
|
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.
?
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.
Looks good; one weird space diff, but that's likely test cruft?
Yeah, exactly. Just wanted to demonstrate what it would look like, but not needed and reverted.
Remove the changes used to trigger the workflows as an example. Not needed for the PR.
cd81c5e
Removed the whitespace changes, but I it would be helpful to get answers to the above open questions before merging. |
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.
Still approve, but also still some weird whitespace diffs?
where @pearsonca ? |
I'm also a bit confused about this one:
|
Changed the default python version to 3.11 from 3.11 after now having merged GH-280.
Split the "unit-tests" action into multiple actions, currently one for each package contained within the
flepiMoP
repo. Also updated checkout from v3 to v4 to address node16 deprecation warnings and swapped ubuntu 20.04 for ubuntu latest. Changed thegempyor
CI to not print stdout and exit on first failure.See GH-278.