Skip to content

Amend upstream-dev GitHub action + Bug fixes #4604

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

Merged
merged 14 commits into from
Dec 5, 2020

Conversation

andersy005
Copy link
Member

@andersy005 andersy005 commented Nov 23, 2020

@andersy005 andersy005 mentioned this pull request Nov 23, 2020
Copy link
Collaborator

@keewis keewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me. I don't know enough about github actions to tell whether this actually works, though.

We might be able to avoid the extra step, but this comes at the cost of a slightly higher complexity (see below).

Copy link
Collaborator

@keewis keewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I looked over the workflow file and noticed a few more things I would change.

Also, we should probably refactor the parse script, I think being able to pass the files via command line helps a lot when testing the script locally. I added a modified version to my test project which parses the short test summary info lines (but feel free to edit it if you think something is hard to read or if it is too fragile). The call in the CI file would then have to be

shopt -s globstar
python .github/workflows/parse_logs.py logs/**/*-log

Edit: actually, let's make that a new PR

@andersy005
Copy link
Member Author

@keewis,

When you get a chance, this is ready for another round of review...

Copy link
Collaborator

@keewis keewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, @andersy005, looks good to me.

@mathause
Copy link
Collaborator

mathause commented Dec 4, 2020

One more point - now the Actions also run on our personal forks. Is that something we want or should/ can this be disabled?

@keewis
Copy link
Collaborator

keewis commented Dec 4, 2020

I don't think we should do that, running the same CI on the same code multiple times in parallel doesn't make much sense. We might be able to stop that by tweaking the on section, but I would fix that in a new PR.

@keewis
Copy link
Collaborator

keewis commented Dec 4, 2020

alright then, let's merge on green.

This is also for a different PR, but maybe we can add a "import xarray" step. This is useful because in case some required dependencies are missing (like numpy, see #4640) we can skip running the tests: they would fail anyway.

@keewis keewis closed this Dec 4, 2020
@keewis keewis reopened this Dec 4, 2020
@keewis keewis closed this Dec 4, 2020
@keewis keewis reopened this Dec 4, 2020
@dcherian
Copy link
Contributor

dcherian commented Dec 5, 2020

Thanks @andersy005 & @keewis !

@keewis keewis merged commit f478335 into pydata:master Dec 5, 2020
@andersy005 andersy005 deleted the bugfix/upstream-dev-ci branch December 5, 2020 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

mamba does not use strict channel priority (in our CI) failing nightly CI
4 participants