** Summary changed: - src:r-cran-dendextend: fails to migrate to testing for too long + r-cran-dendextend: autopkgtest failure
** Description changed: - Imported from Debian bug http://bugs.debian.org/1099069: + Imported from Debian bug https://bugs.debian.org/1102548: - [<email.message.EmailMessage object at 0x7f03ba3a0730>, - <email.message.EmailMessage object at 0x7f03ba3a05b0>] + Source: r-cran-dendextend + Version: 1.19.0+dfsg-1 + Severity: serious - Dear maintainer(s), + https://tracker.debian.org/pkg/r-cran-dendextend - 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:r-cran-dendextend has been trying to - migrate for 34 days [2], hence this bug report. The current output of - the migration software for this package is copied to the bottom of this - report and should list the reason why the package is blocked. + Issues preventing migration: + ∙ ∙ autopkgtest for r-cran-dendextend/1.19.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻ - If a package is out of sync between unstable and testing for a longer - period, this usually means that bugs in the package in testing cannot be - fixed via unstable. Additionally, blocked packages can have impact on - other packages, which makes preparing for the release more difficult. - Finally, it often exposes issues with the package and/or its - (reverse-)dependencies. We expect maintainers to fix issues that hamper - the migration of their package in a timely manner. - 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. - - This bug submission immediately closes the bug with the version in - unstable, so if that version or a later version migrates, this bug will - no longer affect testing. This bug is also tagged to only affect sid and - trixie, so it doesn't affect (old-)stable. - - 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. - - This bug report has been automatically generated and has only been sent - manually. If you have any comments with regards to the content or the - process, please reach out to me. - - Paul - - [1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html - [2] https://qa.debian.org/excuses.php?package=r-cran-dendextend + ... + 135s [ FAIL 1 | WARN 390 | SKIP 0 | PASS 872 ] + 135s + 135s == Failed tests ================================================================ + 135s -- Failure ('test-untangle.R:380:4'): untangle_DendSer works ------------------- + 135s `best_entanglement` not identical to 0. + 135s 1/1 mismatches + 135s [1] 0.0143 - 0 == 0.0143 + 135s + 135s [ FAIL 1 | WARN 390 | SKIP 0 | PASS 872 ] + 135s Error: Test failures + 135s Execution halted + 136s autopkgtest [21:27:26]: test run-unit-test: -----------------------] + 136s autopkgtest [21:27:26]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - + 136s run-unit-test FAIL non-zero exit status 1 + ... ** Bug watch added: Debian Bug tracker #1102548 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102548 ** Changed in: r-cran-dendextend (Debian) Status: Fix Released => Unknown ** Changed in: r-cran-dendextend (Debian) Remote watch: Debian Bug tracker #1099069 => Debian Bug tracker #1102548 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103847 Title: r-cran-dendextend: autopkgtest failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r-base/+bug/2103847/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
