Re: Bug#1022571: transition: pandas 1.3 -> 1.5
Hi Graham, Am Wed, Jan 25, 2023 at 02:28:37PM +0200 schrieb Graham Inggs: > On Wed, 25 Jan 2023 at 11:43, Andreas Tille wrote: > > I was motivated for this patch by Diane's statement on the Debian Med > > matrix channel that dask and dask.distributed are interconnected. If > > the autopkgtest on Salsa CI[4] would have passed I would have uploaded. > > We will temporarily remove dask.distributed from testing, which should > unblock dask and pandas. Thanks a lot! > No uploads please, until dask and pandas have migrated. Yep Andreas. -- http://fam-tille.de
Re: Bug#1022571: transition: pandas 1.3 -> 1.5
Hi Rebecca, Andreas On Wed, 25 Jan 2023 at 11:43, Andreas Tille wrote: > I was motivated for this patch by Diane's statement on the Debian Med > matrix channel that dask and dask.distributed are interconnected. If > the autopkgtest on Salsa CI[4] would have passed I would have uploaded. We will temporarily remove dask.distributed from testing, which should unblock dask and pandas. No uploads please, until dask and pandas have migrated. Regards Graham
Re: Bug#1022571: transition: pandas 1.3 -> 1.5
Hi Graham Am Tue, Jan 24, 2023 at 12:50:41PM +0200 schrieb Graham Inggs: > > On Tue, 24 Jan 2023 at 00:16, Rebecca N. Palmer > wrote: > > The remaining autopkgtest failures blocking pandas are: > > - dipy/amd64 and snakemake/i386 look like random flakiness: please retry > > them. (I think DMs can't use the self-service interface.) Or for dipy, > > see #1029533 for a possible fix. > > These have cleared up. > > > - python-xarray/i386 looks like xarray not pandas: see #1004869. > > Sometimes britney is too greedy and pins too many packages from > unstable. I managed to find the right combination [1] and got the > test to pass without python-xarray. Thanks a lot. > > - dask and dask.distributed have to go together, with or before pandas. > > There's nothing in the currently uploaded packages that specifies > this, although I do see a commit on salsa [2]. I was motivated for this patch by Diane's statement on the Debian Med matrix channel that dask and dask.distributed are interconnected. If the autopkgtest on Salsa CI[4] would have passed I would have uploaded. Unfortunately I have no idea how to deal with those PytestUnraisableExceptionWarnings raised in this test and thus I did not upload. > I tried running dask.distributed's autopkgtest with dask and itself > from unstable [3], but no luck. Diane, could you please comment on this or at least throw some ENOTIME error to let others know. Thanks a lot for you contribution in any case Andreas. > [1] https://ci.debian.net/packages/p/python-xarray/testing/i386/ > [2] > https://salsa.debian.org/python-team/packages/dask.distributed/-/commit/9df3fe1a0ea7538f742ebb162379e3cd50b388e6 > [3] https://ci.debian.net/packages/d/dask.distributed/testing/amd64/ [4] https://salsa.debian.org/python-team/packages/dask.distributed/-/jobs/3834919 -- http://fam-tille.de
Re: Bug#1022571: transition: pandas 1.3 -> 1.5
Hi Rebecca On Tue, 24 Jan 2023 at 00:16, Rebecca N. Palmer wrote: > The remaining autopkgtest failures blocking pandas are: > - dipy/amd64 and snakemake/i386 look like random flakiness: please retry > them. (I think DMs can't use the self-service interface.) Or for dipy, > see #1029533 for a possible fix. These have cleared up. > - python-xarray/i386 looks like xarray not pandas: see #1004869. Sometimes britney is too greedy and pins too many packages from unstable. I managed to find the right combination [1] and got the test to pass without python-xarray. > - dask and dask.distributed have to go together, with or before pandas. There's nothing in the currently uploaded packages that specifies this, although I do see a commit on salsa [2]. I tried running dask.distributed's autopkgtest with dask and itself from unstable [3], but no luck. Regards Graham [1] https://ci.debian.net/packages/p/python-xarray/testing/i386/ [2] https://salsa.debian.org/python-team/packages/dask.distributed/-/commit/9df3fe1a0ea7538f742ebb162379e3cd50b388e6 [3] https://ci.debian.net/packages/d/dask.distributed/testing/amd64/
Re: Bug#1022571: transition: pandas 1.3 -> 1.5
The remaining autopkgtest failures blocking pandas are: - dipy/amd64 and snakemake/i386 look like random flakiness: please retry them. (I think DMs can't use the self-service interface.) Or for dipy, see #1029533 for a possible fix. - python-xarray/i386 looks like xarray not pandas: see #1004869. - dask and dask.distributed have to go together, with or before pandas.
Re: Bug#1022571: transition: pandas 1.3 -> 1.5
skbio is fixed, ulmo is maybe fixed but untested. dask is unclear (see #1027254 for details): it looks like it's probably fixable, but I don't have an actual working fix yet. There has been no response from its maintainers.
