Downstream repositories, on which we should test zarr/master

[Carreau]

• xarray
• ome-zarr https://github.com/ome/ome-zarr-py ? (Add testing of Zarr development branch ome/ome-zarr-py#66)
• https://github.com/constantinpape/zarr_implementations (Test using zarr-dev to potentially catch regressions. zarr_implementations#15)
• https://github.com/ome/omero-cli-zarr

[jakirkham]

cc @rabernat @joshmoore

[jakirkham]

cc @constantinpape

[jakirkham]

For context, we are considering changes like PR ( #612 ), which wouldn't expect to cause issues for downstream, but it would be nice to confirm that somehow. Either by testing here or testing on the downstream repos themselves.

[jhamman]

FWIW, Xarray has recently added a nightly ci build that includes zarr-master (example).

[rabernat]

One idea would be to have a dedicated integration test repo for zarr, xarray, dask, and fsspec that would help cover the many edge cases that arise when these libraries all interact.

[jakirkham]

cc @martindurant

[martindurant]

Some downstreams (fsspec/s3fs) are tested directly in zarr's suite. Similarly, some combinations of dask/xarray are already tested in places, including their own repos.
It's fairly typical to see CI runs that install a variety of "dev" packages from the source repos.

Testing a workflow that touches all of the parts is tricky, and unlikely to catch the corner cases that arise in real work. For example, many s3 problems are around real cluster use and auth, which is very hard to test against. rechunker I suppose uses everything, but what range of likely usage patterns does it cover?

[Carreau]

FWIW, Xarray has recently added a nightly ci build that includes zarr-master (example).

Good; so we are confident that if something break upstream, a bug will be fixed fast :-)

[joshmoore]

#668 (comment) One idea would be to have a dedicated integration test repo for zarr, xarray, dask, and fsspec...

I don't have an immediate driver for xarray, but I was certainly considering adding to @constantinpape's zarr_implementations for example different versions & at least a few different cloud backends. If such a test suite appears elsewhere, though, happy to adapt.

[jrbourbeau]

We added Zarr master to Dask's upstream CI build in dask/dask#6932

[Carreau]

Awesome !