Bug#1030096: #1030096 dask.distributed autopkgtest fail
I currently have this in a state where it sometimes succeeds and sometimes doesn't: https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/tree/fix1030096 Tests I've seen to fail multiple times (and don't have a fix for): test_balance_expensive_tasks[enough work to steal] https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902376 (Seems to be the most common problem. Using @pytest.mark.flaky to try 3 times doesn't seem to have helped, suggesting that if it fails once it keeps failing in that run. Applying part of upstream pull 7253 seemed to make things worse, but I haven't tried applying the whole thing.) test_popen_timeout https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902745 Tests I've seen to fail once: test_stress_scatter_death https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3902040 test_tcp_many_listeners[asyncio] https://salsa.debian.org/rnpalmer-guest/dask.distributed/-/jobs/3896327
Bug#1030096: #1030096 dask.distributed autopkgtest fail
Am Sat, Feb 04, 2023 at 10:43:59PM + schrieb Rebecca N. Palmer: > That removed most of the test failures, but there seem to be a few > apparently random ones left (2 runs both failed, but with different errors). > > On 04/02/2023 21:35, Andreas Tille wrote: > > Any reason to not push to master directly? > > I don't do that with packages that aren't mine. Also see above. Per our team policy that's fine and simply easier for other team members. Thanks a lot for your work Andreas. -- http://fam-tille.de
Bug#1030096: #1030096 dask.distributed autopkgtest fail
That removed most of the test failures, but there seem to be a few apparently random ones left (2 runs both failed, but with different errors). On 04/02/2023 21:35, Andreas Tille wrote: Any reason to not push to master directly? I don't do that with packages that aren't mine. Also see above.
Bug#1030096: #1030096 dask.distributed autopkgtest fail
Am Sat, Feb 04, 2023 at 06:20:32PM + schrieb Rebecca N. Palmer: > I have an attempt to fix this in Salsa now (in my fork), but it hasn't had > time to run the tests yet, so I don't know whether it works. Any reason to not push to master directly? > Note the above mention that if we lose dask.distributed then we lose Spyder, > which makes this a bigger issue than I initially thought. We should definitely keep dask.distributed. Kind regards Andreas. -- http://fam-tille.de
Bug#1030096: #1030096 dask.distributed autopkgtest fail
I have an attempt to fix this in Salsa now (in my fork), but it hasn't had time to run the tests yet, so I don't know whether it works. Note the above mention that if we lose dask.distributed then we lose Spyder, which makes this a bigger issue than I initially thought.
