testing migrations
-
excuses:
- Migration status for ruby-process-metrics (0.11.1-2 to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for ruby-async-container-supervisor/0.10.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
- ∙ ∙ Autopkgtest for ruby-memory-leak/0.10.3-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, loong64: Test triggered, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
- ∙ ∙ Autopkgtest for ruby-process-metrics/0.13.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, loong64: Test triggered, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Test triggered
- ∙ ∙ Piuparts check waiting for test results - https://piuparts.debian.org/sid/source/r/ruby-process-metrics.html
- ∙ ∙ Lintian check waiting for test results - info
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ 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/ruby-process-metrics.png){kind=link}