Your message dated Wed, 5 Feb 2025 19:30:01 +0100
with message-id <4c10cc7e-6633-4504-b194-5ce0730a7...@debian.org>
and subject line Re: Bug#1095200: unblock rust-sqlx/0.8.3-1
rust-sqlx-core/0.8.3-1
has caused the Debian Bug report #1095200,
regarding unblock rust-sqlx/0.8.3-1 rust-sqlx-core/0.8.3-1
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 ow...@bugs.debian.org
immediately.)
--
1095200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
rust-sqlx-core and rust-sqlx seem to be blocked by some autopkgtest snarlups,
particularly 3 autopkgtests seem to be stuck in "test in progress".
The test for rust-ognibuild with the new rust-sqlx on arm64 seems to have
passed several days ago according to the logs on ci.debian.net but this
doesn't seem to have been picked up by britney.
The tests for the new versions of rust-sqlx and rust-sqlx-macros on
riscv64 do not seem to have been run, nor do they seem to be pending.
I understand that the tests are blacklisted on riscv64, but my normal
experiance with blacklisted tests is they still result in a "fail" being
logged on debci, which britney then picks up as "not a regression", this
doesn't seem to be happening here.
Can someone take a look at what is going on and either fix the snarlups
or override them so the packages can migrate to testing.
--- End Message ---
--- Begin Message ---
Hi Peter,
On 05-02-2025 08:04, Peter Green wrote:
rust-sqlx-core and rust-sqlx seem to be blocked by some autopkgtest
snarlups,
particularly 3 autopkgtests seem to be stuck in "test in progress".
These packages migrated by themselves now. (And I currently see: "Test
in progress (will not be considered a regression)", so, unless I'm
mistaken, it was not because of that.
I understand that the tests are blacklisted on riscv64, but my normal
experiance with blacklisted tests is they still result in a "fail" being
logged on debci, which britney then picks up as "not a regression", this
doesn't seem to be happening here.
We changed debci:
https://salsa.debian.org/ci-team/debci/-/merge_requests/289
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
