test_concat_compat FutureWarning: In a future version of xarray the default value for join will change from join='outer' to join='exact'. This change will result in the following ValueError:cannot be aligned with join='exact' because index/labels/sizes are not equal along these coordinates (dimensions): 'y' ('y',) The recommendation is to set join explicitly for this case.

test_concat_second_empty FutureWarning: In a future version of xarray the default value for compat will change from compat='equals' to compat='override'. This change will result in the following ValueError: Cannot specify both data_vars='different' and compat='override'. The recommendation is to set compat explicitly for this case.

test_concat_multiple_datasets_missing_vars[False] FutureWarning: In a future version of xarray the default value for data_vars will change from data_vars='all' to data_vars='minimal'. This is likely to lead to different results when multiple datasets have matching variables with overlapping values. To opt in to new defaults and get rid of these warnings now use `set_options(use_new_combine_kwarg_defaults=True) or set data_vars explicitly.

TestConcatDataset.test_concat_simple[dim1-True-different] FutureWarning: In a future version of xarray the default value for compat will change from compat='equals' to compat='override'. This change will result in the following ValueError: Cannot specify both coords='different' and compat='override'. The recommendation is to set compat explicitly for this case.

TestConcatDataset.test_concat_simple[dim2-False-different] FutureWarning: In a future version of xarray the default value for compat will change from compat='equals' to compat='override'. This change will result in the following ValueError: Cannot specify both coords='different' and compat='override'. The recommendation is to set compat explicitly for this case.

TestConcatDataset.test_concat_merge_variables_present_in_some_datasets FutureWarning: In a future version of xarray the default value for data_vars will change from data_vars='all' to data_vars='minimal'. This is likely to lead to different results when multiple datasets have matching variables with overlapping values. To opt in to new defaults and get rid of these warnings now use `set_options(use_new_combine_kwarg_defaults=True) or set data_vars explicitly.

TestConcatDataset.test_concat_coords_kwarg[dim1-different] FutureWarning: In a future version of xarray the default value for data_vars will change from data_vars='all' to data_vars='minimal'. This is likely to lead to different results when multiple datasets have matching variables with overlapping values. To opt in to new defaults and get rid of these warnings now use `set_options(use_new_combine_kwarg_defaults=True) or set data_vars explicitly.

TestConcatDataset.test_concat_coords_kwarg[dim1-minimal] FutureWarning: In a future version of xarray the default value for data_vars will change from data_vars='all' to data_vars='minimal'. This is likely to lead to different results when multiple datasets have matching variables with overlapping values. To opt in to new defaults and get rid of these warnings now use `set_options(use_new_combine_kwarg_defaults=True) or set data_vars explicitly.

TestConcatDataset.test_concat_coords_kwarg[dim1-all] FutureWarning: In a future version of xarray the default value for data_vars will change from data_vars='all' to data_vars='minimal'. This is likely to lead to different results when multiple datasets have matching variables with overlapping values. To opt in to new defaults and get rid of these warnings now use `set_options(use_new_combine_kwarg_defaults=True) or set data_vars explicitly.

TestConcatDataset.test_concat_coords_kwarg[dim2-different] FutureWarning: In a future version of xarray the default value for compat will change from compat='equals' to compat='override'. This change will result in the following ValueError: Cannot specify both coords='different' and compat='override'. The recommendation is to set compat explicitly for this case.

deallocating CachingFileManager(<class 'h5netcdf.core.File'>, <fsspec.implementations.local.LocalFileOpener object at 0x7f4ffc8e5300>, mode='r', kwargs={'invalid_netcdf': None, 'decode_vlen_strings': True, 'driver': None, 'phony_dims': 'access'}, manager_id='59371486-3494-4a97-a19e-cb00ca42ac68'), but file is not already closed. This may indicate a bug.

deallocating CachingFileManager(<class 'h5netcdf.core.File'>, <fsspec.implementations.local.LocalFileOpener object at 0x7f4ffc89a320>, mode='r', kwargs={'invalid_netcdf': None, 'decode_vlen_strings': True, 'driver': None, 'phony_dims': 'access'}, manager_id='a3d90233-797e-4d23-abd6-dd72ec8b3163'), but file is not already closed. This may indicate a bug.

deallocating CachingFileManager(<class 'h5netcdf.core.File'>, <fsspec.implementations.local.LocalFileOpener object at 0x7f4ffc8e5300>, mode='r', kwargs={'invalid_netcdf': None, 'decode_vlen_strings': True, 'driver': None, 'phony_dims': 'access'}, manager_id='59371486-3494-4a97-a19e-cb00ca42ac68'), but file is not already closed. This may indicate a bug.

deallocating CachingFileManager(<class 'h5netcdf.core.File'>, <fsspec.implementations.local.LocalFileOpener object at 0x7f4ffc89a320>, mode='r', kwargs={'invalid_netcdf': None, 'decode_vlen_strings': True, 'driver': None, 'phony_dims': 'access'}, manager_id='a3d90233-797e-4d23-abd6-dd72ec8b3163'), but file is not already closed. This may indicate a bug.

invalid value encountered in cast

invalid value encountered in cast

invalid value encountered in cast

invalid value encountered in cast

The experimental Zarr V3 implementation in this version of Zarr-Python is not in alignment with the final V3 specification. This version will be removed in Zarr-Python 3 in favor of a spec compliant version.

The experimental Zarr V3 implementation in this version of Zarr-Python is not in alignment with the final V3 specification. This version will be removed in Zarr-Python 3 in favor of a spec compliant version.

Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.