action needed
The package has not entered testing even though the delay is over
normal
The package has not entered testing even though the 5-day delay is over.
Check why.
testing migrations
-
excuses:
- Migration status for r-cran-markdown (- to 2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for r-cran-bit/4.6.0+dfsg-3: amd64: Test triggered, arm64: Test triggered, armhf: Failed (not a regression) ♻ (reference ♻), i386: Test triggered, loong64: Pass, ppc64el: Test triggered (will not be considered a regression) ♻ (reference ♻), riscv64: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for r-cran-knitr/1.51+dfsg-2: amd64: Test triggered, arm64: Pass, armhf: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), loong64: Pass, ppc64el: Pass, riscv64: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for r-cran-markdown/2.0-1: amd64: Pass, arm64: Pass, armhf: Failed ♻, i386: Failed ♻, loong64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-markdown.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 82 days old (needed 5 days)
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/r/r-cran-markdown.png){kind=link}