Skip to content
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

Schedule upstream dev tests #607

Merged
merged 3 commits into from
Sep 8, 2023
Merged

Conversation

cisaacstern
Copy link
Member

Towards #606

IMO we don't need to be testing against upstream dev versions on every commit of every PR.

This PR instead tests against upstream dev versions once nightly, which should still allow us to surface any potential issues in a timely fashion, while also reducing clutter on PR commit checks.

@cisaacstern
Copy link
Member Author

This PR also tests against upstream dev installs of zarr-python and apache-beam. Zarr is installed from GitHub, like the other upstream dev requirements. Beam appears to follow a much more regimented release candidate cycle than any of the other upstream dev requirements, so we install that from any available release candidates instead of from GitHub.

@cisaacstern
Copy link
Member Author

cisaacstern commented Sep 8, 2023

This gets us down to only 6 checks per commit currently, nice! Much more approachable and developer-friendly IMHO. 😃

@cisaacstern cisaacstern merged commit f094b02 into main Sep 8, 2023
@cisaacstern cisaacstern deleted the schedule-upstream-dev-tests branch September 8, 2023 06:20
@cisaacstern cisaacstern restored the schedule-upstream-dev-tests branch September 8, 2023 06:23
@cisaacstern cisaacstern deleted the schedule-upstream-dev-tests branch September 8, 2023 06:23
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.

1 participant