pytest on main fails since 8c3d07e landed: https://github.com/xarray-contrib/xarray-spatial/actions/runs/27278776057
FAILED xrspatial/tests/test_reproject_streaming_3101.py::TestStreaming3D::test_3d_source_streams - [XPASS(strict)] 2-D output buffer vs 3-D tiles, see #3100
Two PRs raced. #3111 (1a63f90, merged 13:11 UTC) fixed the 3-D (y, x, band) crash in _reproject_streaming by carrying the band axis through the output allocation. #3118 (8c3d07e, merged 13:13 UTC) added TestStreaming3D::test_3d_source_streams with @pytest.mark.xfail(strict=True, raises=ValueError, reason="2-D output buffer vs 3-D tiles, see #3100"), and its CI ran before #3111 landed. On current main the test passes, so the strict xfail fails the whole suite.
The test already says what to do: "Once #3100 is fixed the xfail comes off and the streaming result must match the in-memory 3-D path." Take the xfail marker off and let the assertions run; they compare streaming output against the in-memory path, which is exactly the post-#3111 contract.
This also turns every open PR's merge-ref CI red (e.g. #3173).
pyteston main fails since 8c3d07e landed: https://github.com/xarray-contrib/xarray-spatial/actions/runs/27278776057Two PRs raced. #3111 (1a63f90, merged 13:11 UTC) fixed the 3-D
(y, x, band)crash in_reproject_streamingby carrying the band axis through the output allocation. #3118 (8c3d07e, merged 13:13 UTC) addedTestStreaming3D::test_3d_source_streamswith@pytest.mark.xfail(strict=True, raises=ValueError, reason="2-D output buffer vs 3-D tiles, see #3100"), and its CI ran before #3111 landed. On current main the test passes, so the strict xfail fails the whole suite.The test already says what to do: "Once #3100 is fixed the xfail comes off and the streaming result must match the in-memory 3-D path." Take the xfail marker off and let the assertions run; they compare streaming output against the in-memory path, which is exactly the post-#3111 contract.
This also turns every open PR's merge-ref CI red (e.g. #3173).