Upstream stays red after #9351: behind the Bokeh hang it fixed there is a second, unrelated failure, dark since 2026-07-31.
What happens. scipy now warns on every *_matrix instantiation (scipy/sparse/_matrix.py: "…is being replaced by …_array. … The spmatrix classes will be removed no earlier than v2.2."). distributed's pytest config escalates warnings to errors (filterwarnings = ["error", …]), so all 14 parametrizations of distributed/protocol/tests/test_scipy.py::test_serialize_scipy_sparse fail:
E DeprecationWarning: coo_matrix is being replaced by coo_array.
The first run to show it is the #9351 merge push itself (c88eb0b8, 2026-08-20): 14 failed, 2442 passed, 125 skipped in ubuntu-latest nightly test-ci not ci1 (job), the scipy cases being the only failures. The existing scipy entry in pyproject.toml's filterwarnings ("Please use dok_matrix from the scipy.sparse namespace…") matches the previous deprecation wave's message, not this one.
Why nobody could see it. Since 07-31 the Bokeh regression (#9350) hung this same job, so the nightly … not ci1 leg of every sampled scheduled run (07-31, 08-05, 08-10, 08-19) died at the 120-minute timeout as cancelled — no pytest summary, and upstream.yml uploads no artifacts. Scheduled runs have been red nightly since 07-31; last green was 07-30. #9351 unblocked the job; this failure is what was underneath, and the next scheduled run will surface it again.
Fix, your call: a scoped ignore beside the existing dok_matrix entry — something like '''ignore:\w+_matrix is being replaced by \w+_array''' (the matrix classes stay supported until scipy 2.2, and the test deliberately covers all seven) — or start migrating distributed/protocol/scipy.py and its test to sparse arrays now. I'd take the scoped ignore.
This report was researched and written by an AI agent (Claude Code) operated by @glaziermag. Every run link, job conclusion, and attribution above was re-verified against the GitHub API before filing.
Upstream stays red after #9351: behind the Bokeh hang it fixed there is a second, unrelated failure, dark since 2026-07-31.
What happens. scipy now warns on every
*_matrixinstantiation (scipy/sparse/_matrix.py: "…is being replaced by …_array. … The spmatrix classes will be removed no earlier than v2.2.").distributed's pytest config escalates warnings to errors (filterwarnings = ["error", …]), so all 14 parametrizations ofdistributed/protocol/tests/test_scipy.py::test_serialize_scipy_sparsefail:The first run to show it is the #9351 merge push itself (c88eb0b8, 2026-08-20):
14 failed, 2442 passed, 125 skippedinubuntu-latest nightly test-ci not ci1(job), the scipy cases being the only failures. The existing scipy entry inpyproject.toml's filterwarnings ("Please usedok_matrixfrom thescipy.sparsenamespace…") matches the previous deprecation wave's message, not this one.Why nobody could see it. Since 07-31 the Bokeh regression (#9350) hung this same job, so the
nightly … not ci1leg of every sampled scheduled run (07-31, 08-05, 08-10, 08-19) died at the 120-minute timeout ascancelled— no pytest summary, andupstream.ymluploads no artifacts. Scheduled runs have been red nightly since 07-31; last green was 07-30. #9351 unblocked the job; this failure is what was underneath, and the next scheduled run will surface it again.Fix, your call: a scoped ignore beside the existing dok_matrix entry — something like
'''ignore:\w+_matrix is being replaced by \w+_array'''(the matrix classes stay supported until scipy 2.2, and the test deliberately covers all seven) — or start migratingdistributed/protocol/scipy.pyand its test to sparse arrays now. I'd take the scoped ignore.This report was researched and written by an AI agent (Claude Code) operated by @glaziermag. Every run link, job conclusion, and attribution above was re-verified against the GitHub API before filing.