[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1031128: marked as done (release.debian.org: please suppress ppc64el and s390x CI tests for src:rust-ureq)

Your message dated Sun, 12 Feb 2023 17:11:01 +0100
with message-id <167621826169.3113738.16732138609823241105@auryn.jones.dk>
and subject line Re: Bug#1031128: release.debian.org: please suppress ppc64el and s390x CI tests for src:rust-ureq
has caused the Debian Bug report #1031128,
regarding release.debian.org: please suppress ppc64el and s390x CI tests for src:rust-ureq
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1031128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031128
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

The package src:rust-urew is currently blocked from entering testing.

CI tests are generally not completing, as tracked as bug#1030883.

For two arches, ppc64el and s390x, CI tests now complete which reveals
that on those arches the CI infrastructure bogusly thinks that a
dependency on the virtual package
librust-rustls-0.20+dangerous-configuration-dev should be resolved as
arch-specific package which is not true for more than a week now.

Please therefore mark rust-urew as ignore CI tests for ppc64el and
s390x since those test environments are apparently broken.

Kind regards,

 - Jonas

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPooSAACgkQLHwxRsGg
ASFhPA/9FGuD+NW8pl2FiAGqwUAUFRvpxji8PUyDoWGxopsURUeT0iwHrigRiJG/
YAhrN7I1oY3qNDXT4PevH3q39XD7zMDpeFU+Yg/b/VFND1Htl3B3GW9qQEnVeSpG
yy/KMHfznxPMtni47CUFEHxbfPBnLOePJzCfjSM/kL0r7LheOMuXwOtxKbrVRcP+
0gmAK5DUikXfvwjOL+QsVlkpd2hwJhNMmS+WwLZRHRpX0nzRKJsDHUP+d6dZkIKW
ex47RpDWvFEeSeBfXK67dKLdKDMzKsBx/67iXL7S6XYeU642+DT86hWow7Kqp88e
sDNDu9CSV+NzsYkGS8UFRtBne5RfMps+JiuJIb1qdX8Q5+YCMtRg61F+ml+yUOwA
cWZxEohddH0rOObE27mrQvNGP+ZtRXeEi7PgnMHN5Hy0CdC4mIY1xSzKGrD1M2sh
OasZT6X4KcVtI2mouBs+tJr2pJw9js7cEiU+F5LOLUh424YMcBhMzEscKoOWlAm7
PdJDEOiW/n4j6F+ko+Sr468rZEKLrc0aYrZFuRH/iw+HHLEqqG6cAVBLJghPtiwK
KHFekI3XyNMpojyxCAjarZMzPiB0igaSbfE1EtZ2oeFlnYQY5ND2kz1NOAwL57zE
7j4LVaobwyh4jvS+P+6ibHY77TKvD9Q2GYPPr3J0it9P5WInzys=
=Pqlk
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Quoting Paul Gevers (2023-02-12 16:49:04)
> On 12-02-2023 09:19, Jonas Smedegaard wrote:
> > Package: release.debian.org
> > Severity: important
>              ^^^^^^^^^
> Please don't do this with bugs against release.debian.org. It makes our 
> flow worse instead of helping.

Noted!


> > The package src:rust-urew is currently blocked from entering testing.
> 
> I suspect you typoed (twice, below as well) and you meant rust-ureq (as 
> in the subject).

Whoops, yes indeed.


> > CI tests are generally not completing, as tracked as bug#1030883.
> 
> Ack. That bug has a fix pending, let's wait until its fixed and we can 
> confirm all other architectures are OK (hence the moreinfo tag). You can 
> easily work around this yourself by uploading a new version without 
> testnames that start with a hyphen.

Ahhh.  You already explained the cause of the problem, but I missed the
crucial detail that it was an explicit initial hyphen that triggered the
problem.  Sorry for being dense - I will correct that now.


> > For two arches, ppc64el and s390x, CI tests now complete which reveals
> > that on those arches the CI infrastructure bogusly thinks that a
> > dependency on the virtual package
> > librust-rustls-0.20+dangerous-configuration-dev should be resolved as
> > arch-specific package which is not true for more than a week now.
> > 
> > Please therefore mark rust-urew as ignore CI tests for ppc64el and
> > s390x since those test environments are apparently broken.
> 
> Please don't use that tone. The test environments are NOT broken, it's 
> your package that can't be installed. If anything, it's your package 
> that's "broken" on those architectures. As I explained in bug #1030957 
> and you acknowledged, librust-rustls-dev depend on librust-ring-*-dev 
> which isn't available everywhere. Nothing really broken, just regular 
> behavior of arch:all binaries that have arch:non-all (transverse) 
> dependencies that aren't available everywhere. As mentioned earlier, you 
> brought this regression onto yourself.
> 
> If you decide to fix all this yourself by uploading a new version with 
> the testname changed and the skip-not-installable restriction added 
> back, then please close this bug, as then you don't need to wait for the 
> fix in debci.

My sincere apology.  Unitl now I was still under the impression that I
had done nothing wrong (I misunderstood the trigger as being the word
"gzip" that the CI tooling wrongly processed as an executable instead of
a test name).

Additionally I misunderstood this bug as consistently causing failure to
process CI, and therefore I filed this *different* bug for the issue of
two CI environments completing-but-failing.

Closing this as a non-bug.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


--- End Message ---
Reply to: