On Thu, 2023-02-09 at 07:44 +0000, Rebecca N. Palmer wrote: > On 09/02/2023 06:36, Diane Trout wrote: > > Also there's still some flaky tests as the rebuild triggered by my > > just > > committing the changelog release had a failure in > > "test_release_retry" > > I don't think I've seen that particular one before, though like > several > others it's a warning being treated as an error because > dask.distributed > now does that (in setup.cfg).
Would it make sense to drop those errors back to warnings, and do you know enough about the setup.cfg language to do it quickly? > > debci doesn't appear to have run yet. (If it does and fails, note > that > there's a retry button next to failure reports. Given how tight we > are > on time (we need to be in testing by the 12th), I'd rather not re- > upload > (restarting the migration clock) if we don't have to.) It says it failed on 4 tests on ci for amd64 but I could only find the traceback for test_default_5 with a bunch of OS errors having run out of file handles. I went ahead and requested another run for the failed amd64 run and left the passing arm64 run alone. > > Also, we need to close this bug (by email _not_ by uploading). Also how did numba 0.56.4-1 get overridden to be back in testing? Can we get dask.distributed forced back in? It looks like it mostly works, it feels like we're mostly fighting over it not being robust to environment specific issues. Diane
