Scrub Obsolete - maven-resolver
Recent merge proposals
The codemod failed to run for some reason, and didn't report why. This is almost always a bug in the codemod.
Run locally
More details
Historical runs
- run-disappeared: Jenkins lists job 1130783 for run da4eb1eb-2633-4cd8-9390-466d7e7850e7 as failed
- command-failed: Script ['deb-scrub-obsolete', '--keep-minimum-depends-versions'] failed to run with code 1
- nothing-new-to-do: No changes made
- worker-timeout: No keepalives received in 1:00:01.787117.
- success: Remove constraints unnecessary since buster.
- nothing-new-to-do: No changes made
- success: Remove constraints unnecessary since buster.
- worker-failure: ImportError: cannot import name 'MissingChangelogError' from 'breezy.plugins.debian.vcs_up_to_date' (/usr/local/lib/python3.10/dist-packages/breezy/plugins/debian/vcs_up_to_date.py)
- codemod-command-failed: Script ['deb-scrub-obsolete'] failed to run with code 1
- codemod-command-failed: Script ['deb-scrub-obsolete'] failed to run with code 1
- codemod-command-failed: Script ['deb-scrub-obsolete'] failed to run with code 1
- codemod-command-failed: Script ['deb-scrub-obsolete'] failed to run with code 1
- run-disappeared: Worker started processing new run rather than eede8622-cdb9-48cc-b809-c2b4f3c00c4a
- unable-to-find-upstream-tarball: Unable to find the needed upstream tarball for maven-resolver, version 110.79.
- unable-to-find-upstream-tarball: Unable to find the needed upstream tarball for maven-resolver, version 3.10.2.
- inconsistent-source-format: Inconsistent source format between version and source format
- build-failed-stage-explain-bd-uninstallable: build failed stage explain-bd-uninstallable
- 502-bad-gateway: Unexpected HTTP status 502 for https://salsa.debian.org/java-team/maven-resolver.git/info/refs?service=git-upload-pack: Unable to handle http code: Bad Gateway