On Fri, 2023-02-10 at 08:44 +0530, Nilesh Patra wrote: > Control: fixed -1 2022.12.1+ds.1-2 > > Some tests passed after I put it for (multiple) retries. The > current state looks fine > > https://qa.debian.org/excuses.php?package=dask.distributed > > But I am not sure if this counter would be set to 2 days (from 5 > days)
That explains why the tests suddenly passed when i wasn't looking. When I'd last looked in the morning most of them were marked failed. > or not -- will likely need to ask release team. > In any case it might be a nice idea to hold off any further uploads > until this migrates. > Yeah I need to beg the release team for forgiveness. Though I made two changes that should dramatically increase the odds of the tests passing. One I told it to skip all the "isinstalled" marked tests, which are all skipped during build time, and the build seems to run far more reliably. I got the idea because it seemed like the vast majority of test failures are related to the daemons running or failing to shut down. While talking on IRC about dask.distributed problems I learned of the flaky autopkgtest restriction which says the test is expected to fail intermittently and is not suitable for gating continuous integratin. So I marked the current whole autopkgtest run as flaky. So CI should also ignore the results of failed test runs now. When under less time pressure I think a good plan might be two split the tests internally marked as isinstalled or flaky into a separate autopkgtest run that's marked flaky and let the CI gate on the more reliable tests. Diane
signature.asc
Description: This is a digitally signed message part
