testing migrations
-
excuses:
- Migration status for ruby-faraday-retry (2.2.0-2 to 2.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ autopkgtest for ruby-acme-client/2.10.really.2.0.18-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, riscv64: No tests, superficial or marked flaky ♻, s390x: Test triggered
- ∙ ∙ autopkgtest for ruby-faraday-retry/2.3.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, riscv64: No tests, superficial or marked flaky ♻, s390x: Test triggered
- ∙ ∙ autopkgtest for ruby-gh/0.21.0-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, riscv64: Pass, s390x: Test triggered
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-faraday-retry.html
- ∙ ∙ Waiting for reproducibility test results on amd64 - info ♻
- ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/r/ruby-faraday-retry.png){kind=link}