action needed
Debci reports failed tests
high
-
unstable: pass (log)
The tests ran in 0:02:54
Last run: 2026-03-24T23:13:30.000Z
Previous status: unknown
-
testing: fail (log)
The tests ran in 0:01:09
Last run: 2026-05-12T09:21:54.000Z
Previous status: unknown
-
stable: pass (log)
The tests ran in 0:03:53
Last run: 2025-11-09T01:25:49.000Z
Previous status: unknown
testing migrations
-
excuses:
- Migrates after: r-cran-rlang, r-cran-vctrs
- Migration status for r-cran-furrr (0.3.1-2 to 0.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for r-cran-furrr/0.4.0-1: amd64: Pass, arm64: Pass, i386: Test triggered, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Test triggered
- ∙ ∙ Autopkgtest for r-cran-progressr/0.18.0-1: amd64: Pass, arm64: Pass, i386: Test triggered, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Too young, only 2 of 5 days old
- ∙ ∙ Build-Depends(-Arch): r-cran-furrr r-cran-rlang (not considered)
- ∙ ∙ Build-Depends(-Arch): r-cran-furrr r-cran-vctrs (not considered)
- ∙ ∙ Depends: r-cran-furrr r-cran-rlang (not considered)
- ∙ ∙ Depends: r-cran-furrr r-cran-vctrs (not considered)
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-furrr.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/r/r-cran-furrr.png){kind=link}