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

Add testing of Zarr development branch #66

Merged
merged 1 commit into from
Dec 4, 2020
Merged

Conversation

Carreau
Copy link
Contributor

@Carreau Carreau commented Dec 2, 2020

Only on linux and a single version of Python.

This would help to catch potential regressions.

Only on linux and a single version of Python.

This would help to catch potential regressions.
@joshmoore
Copy link
Member

Thanks, @Carreau. Happy to have this in. Also, good to see another working version after the fun of gh-51. Depending on what happens with build.yml, I may refactor this into the existing workflow and use another build dimension for different zarr versions.

@joshmoore joshmoore merged commit b483bc2 into ome:master Dec 4, 2020
@Carreau
Copy link
Contributor Author

Carreau commented Dec 4, 2020

I may refactor this into the existing workflow and use another build dimension for different zarr versions.

I thought about doing this but I believed that testing on only ome zarr version and only linux was sufficient, which would be annoying with adding a dimension.

@joshmoore
Copy link
Member

We'll see ;) We also have a build that switches to a French Locale once a week to help detect bugs.

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.

2 participants