-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Run upstream tests based on commit message #7329
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
Conversation
|
This is really cool! |
|
I was looking at the Xarray repo and noticed they were doing this -- totally agree it's a neat thing to have. We used to have this functionality back when we were on Travis CI, and I recall it being nice to have from time to time |
|
Do you think this will grow to other libraries ? If so, maybe we should rename to something more specific, like |
|
Ah, I mean I was looking at Xarray's own upstream CI in their repo and saw they were able to launch their own upstream CI tests based on |
|
Ah, ok! Thanks for the explanation |
|
This is great! Do you know why |
|
I don't totally remember why. Jim gave something similar a shot in #6196 and I also tried at one point but wasn't able to get things to work easily |
|
Thanks for that context! There is one of these in ci-additional as well for test-hdf. Do you want to convert that one as well in this PR? Also happy to merge as is. |
|
I'm okay limiting the scope of this PR to just upstream. I've opened up #7337 to track doing something similar with HDFS tests |
* upstream/main: Change default branch from master to main (dask#7198) Add Xarray to CI software environment (dask#7338) Update repartition argument name in error text (dask#7336) Run upstream tests based on commit message (dask#7329) Use pytest.register_assert_rewrite on util modules (dask#7278) add example on using specific chunk sizes in from_array() (dask#7330) Move numpy skip into test (dask#7247)
This PR enables us to run an upstream test build when a commit message contains the phrase
test-upstream. We do this by adding a newcheckjob to our existing upstream GHA workflow which utilizesxarray-contrib/ci-triggerto search the corresponding commit message fortest-upstream. If it is found in the commit message then the upstream build is launched otherwise the upstream build is skipped.The extra
checkjob takes ~5 seconds to run, so I don't anticipate it impacting our CI backlog in a meaningful way.Here are a couple of example CI builds which demonstrate the upstream tests being skipped or not:
test-upstreamin the commit messagetest-upstreamin the commit message