Hi Alastair,
python-xarray currently reports several test failures[0]. If the package migrates to testing, it'd fix #1100293[1] which otherwise could cause a lot of AUTORM.
The test failures are on the 32bit archs (armel, armhf, and i386), as well as s390x. The failures on 32bit archs don't look serious to me as they look like either intended for 64bit, or false negatives. In that regard, I have a patch that'd disable those failing tests conditionally on 32bit archs[2]. I can't, however, push it to the team repo since it looks like the changes for the previous upload (as well as the debian tags for the last two uploads) was
not pushed. If my patch seems reasonable to you, I can push it and do a team upload once you push your changes to the repo, or add an MR if you'd prefer that.
As for the test failures on s390x, that comes from uninstallable build-depends
which tracks down to magics++ not building on s390x[3] (and other archs). So either that needs to be fixed, or python-xarray and rdeps have to drop s390x.
[0] https://ci.debian.net/packages/p/python-xarray/
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100293
[2] https://salsa.debian.org/weepingclown/python-xarray/-/commit/23bb201a0ac7ddab59e368cd342516d90ef8e47a
[3] https://buildd.debian.org/status/package.php?p=magics%2B%2B
H Anathanu
A patch to fix this has just been uploaded. Once it is safely tested in experimental, I'll request an unblock.
There was somehow a buggy -2 upload that missed the actual patch in d/rules
Best regards
Alastair
On 19/04/2025 11:56, Ananthu C V wrote:
Hi Alastair,
python-xarray currently reports several test failures[0]. If the package migrates to testing, it'd fix #1100293[1] which otherwise could cause a lot of AUTORM.
The test failures are on the 32bit archs (armel, armhf, and i386), as well as
s390x. The failures on 32bit archs don't look serious to me as they look like
either intended for 64bit, or false negatives. In that regard, I have a patch
that'd disable those failing tests conditionally on 32bit archs[2]. I can't,
however, push it to the team repo since it looks like the changes for the previous upload (as well as the debian tags for the last two uploads) was not pushed. If my patch seems reasonable to you, I can push it and do a team
upload once you push your changes to the repo, or add an MR if you'd prefer that.
As for the test failures on s390x, that comes from uninstallable build-depends
which tracks down to magics++ not building on s390x[3] (and other archs). So
either that needs to be fixed, or python-xarray and rdeps have to drop s390x.
[0] https://ci.debian.net/packages/p/python-xarray/
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100293
[2] https://salsa.debian.org/weepingclown/python-xarray/-/commit/23bb201a0ac7ddab59e368cd342516d90ef8e47a
[3] https://buildd.debian.org/status/package.php?p=magics%2B%2B
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
e: alastair@mckinstry.ie, im: @alastair:mckinstry.ie @amckinstry@mastodon.ie
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
believing the innocent had everything to fear, mostly from the guilty but in the longer term
even more from those who say things like “The innocent have nothing to fear.”
- T. Pratchett, Snuff
Hi Alastair,
It seems to be fine in experimental (though it is only debci-tested on
amd64 and arm64), so please do go ahead and upload -4 to unstable.
You don't need to request an unblock at this stage; see https://release.debian.org/testing/freeze_policy.html#soft
Best wishes,
Julian
On Mon, Apr 21, 2025 at 03:39:21PM +0100, Alastair McKinstry wrote:
H Anathanu
A patch to fix this has just been uploaded. Once it is safely tested in
experimental, I'll request an unblock.
There was somehow a buggy -2 upload that missed the actual patch in d/rules >>
Best regards
Alastair
On 19/04/2025 11:56, Ananthu C V wrote:
Hi Alastair,--
python-xarray currently reports several test failures[0]. If the package >>> migrates to testing, it'd fix #1100293[1] which otherwise could cause a lot >>> of AUTORM.
The test failures are on the 32bit archs (armel, armhf, and i386), as well as
s390x. The failures on 32bit archs don't look serious to me as they look like
either intended for 64bit, or false negatives. In that regard, I have a patch
that'd disable those failing tests conditionally on 32bit archs[2]. I can't,
however, push it to the team repo since it looks like the changes for the >>> previous upload (as well as the debian tags for the last two uploads) was >>> not pushed. If my patch seems reasonable to you, I can push it and do a team
upload once you push your changes to the repo, or add an MR if you'd prefer that.
As for the test failures on s390x, that comes from uninstallable build-depends
which tracks down to magics++ not building on s390x[3] (and other archs). So
either that needs to be fixed, or python-xarray and rdeps have to drop s390x.
[0] https://ci.debian.net/packages/p/python-xarray/
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100293
[2] https://salsa.debian.org/weepingclown/python-xarray/-/commit/23bb201a0ac7ddab59e368cd342516d90ef8e47a
[3] https://buildd.debian.org/status/package.php?p=magics%2B%2B
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
e: alastair@mckinstry.ie, im: @alastair:mckinstry.ie @amckinstry@mastodon.ie >>
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
believing the innocent had everything to fear, mostly from the guilty but in the longer term
even more from those who say things like “The innocent have nothing to fear.”
- T. Pratchett, Snuff
Julian
Hi Alastair
Thanks for working on these failing tests.
I'm not sure that the uploads are going where you intend, however:
$ grep ^python-xarray debian/changelog | head -2 | tac
python-xarray (2025.03.1-2) experimental; urgency=medium
python-xarray (2025.03.1-3) unstable; urgency=medium
$ rmadison -s unstable,experimental python-xarray
python-xarray | 2025.03.1-2 | unstable | source
python-xarray | 2025.03.1-3 | experimental | source
that is, the upload for unstable went to experimental, and the upload for experimental went to unstable. (btw I think this is the sort of thing that lintian will point out if you run it against the .changes file)
That also means that these changes haven't fixed the underlying issue: CI
for 2025.03.1-2 is still failing on multiple architectures (and there are no changes in 2025.03.1-3).
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net
Debian Developer http://www.debian.org/ stuart@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
I've just uploaded -4 to unstable, which is identical to -3 in
experimental but with a new changelog entry:
python-xarray (2025.03.1-4) unstable; urgency=medium
* Team upload
* Push to unstable
-- Julian Gilbey <jdg@debian.org> Mon, 28 Apr 2025 06:43:27 +0100
Best wishes,
Julian
On Fri, Apr 25, 2025 at 03:00:12PM +1000, Stuart Prescott wrote:
Hi Alastair
Thanks for working on these failing tests.
I'm not sure that the uploads are going where you intend, however:
$ grep ^python-xarray debian/changelog | head -2 | tac
python-xarray (2025.03.1-2) experimental; urgency=medium
python-xarray (2025.03.1-3) unstable; urgency=medium
$ rmadison -s unstable,experimental python-xarray
python-xarray | 2025.03.1-2 | unstable | source
python-xarray | 2025.03.1-3 | experimental | source
that is, the upload for unstable went to experimental, and the upload for
experimental went to unstable. (btw I think this is the sort of thing that >> lintian will point out if you run it against the .changes file)
That also means that these changes haven't fixed the underlying issue: CI
for 2025.03.1-2 is still failing on multiple architectures (and there are no >> changes in 2025.03.1-3).
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net
Debian Developer http://www.debian.org/ stuart@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Thank you,
Apologies I've been away and connectivity (and responsiveness) was intermittent.
Regards
Alastair
On 28/04/2025 07:16, Julian Gilbey wrote:
I've just uploaded -4 to unstable, which is identical to -3 in
experimental but with a new changelog entry:
python-xarray (2025.03.1-4) unstable; urgency=medium
* Team upload
* Push to unstable
-- Julian Gilbey <jdg@debian.org> Mon, 28 Apr 2025 06:43:27 +0100
Best wishes,
Julian
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 481 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 11:08:57 |
| Calls: | 9,539 |
| Calls today: | 7 |
| Files: | 13,653 |
| Messages: | 6,139,230 |
| Posted today: | 1 |