action needed
Debci reports failed tests
high
-
unstable: pass (log)
The tests ran in 0:01:47
Last run: 2026-05-28T05:14:27.000Z
Previous status: unknown
-
testing: fail (log)
The tests ran in 0:00:19
Last run: 2026-07-31T09:06:31.000Z
Previous status: unknown
-
stable: pass (log)
The tests ran in 0:02:03
Last run: 2026-07-18T12:11:06.000Z
Previous status: unknown
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:
- Migrates after: dask, flox, python-rioxarray, python-xarray, xarray-sentinel
- Migration status for sarsen (- to 0.9.6-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for sarsen/0.9.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Build-Depends(-Arch): sarsen dask (not considered)
- ∙ ∙ Build-Depends(-Arch): sarsen flox
- ∙ ∙ Build-Depends(-Arch): sarsen python-rioxarray
- ∙ ∙ Build-Depends(-Arch): sarsen python-xarray
- ∙ ∙ Build-Depends(-Arch): sarsen xarray-sentinel
- ∙ ∙ Depends: sarsen dask (not considered)
- ∙ ∙ Depends: sarsen flox
- ∙ ∙ Depends: sarsen python-rioxarray
- ∙ ∙ Depends: sarsen python-xarray
- ∙ ∙ Depends: sarsen xarray-sentinel
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sarsen.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 46 days old (needed 5 days)
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/s/sarsen.png){kind=link}