clone 1059165 -1 reassign -1 nodejs retitle -1 autopkgtest failures on i386 found -1 18.19.0+dfsg-6 block 1059165 by -1 kthxbye
On Wed, Dec 20, 2023 at 08:15:31PM +0100, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing and > unstable for more than 30 days as having a Release Critical bug in testing > [1]. Your package src:zlib has been trying to migrate for 32 days [2]. > Hence, I am filing this bug. The version in unstable triggers autopkgtest > failures in multiple packages (although I suspect that the current dolfin > issues are due to it being flaky). The failure for burp has already a bug > report against that package, which leaves nodejs on i386. ... > This bug will trigger auto-removal when appropriate. As with all new bugs, > there will be at least 30 days before the package is auto-removed. Not sure that's likely in the case of zlib? > If you believe your package is unable to migrate to testing due to issues > beyond your control, don't hesitate to contact the Release Team. There are non-technical issues with me doing active work on nodejs package but from a quick glance the log does not seem particularly plausibly related to zlib, and I note that the failures are not ok 498 parallel/test-debugger-heap-profiler not ok 962 parallel/test-fs-utimes-y2K38 # TODO : Fix flaky test the second of which especially doesn't inspire confidence that this is due to zlib rather than general updates to unstable setting off an already flaky test (eg, the kernel changed timing?). Full log is: https://ci.debian.net/packages/n/nodejs/testing/i386/41176091/ and looking at: https://ci.debian.net/packages/n/nodejs/testing/i386/ there seem to be a number of packages triggering what from spot checks look to be the same or similar issues in nodejs in testing. I frankly don't really know what I'm supposed to do with this, the test results look like noise as far as zlib is concerned so I don't see anything to fix or investigate in the package itself. AFAICT bugs don't get filed for autopkgtest failures like they do for build failures so perhaps this was just missed up until now?
signature.asc
Description: PGP signature
