@juliank, ah, I found another detail. This appears to only break when the package is updated in the ADT testbed. My assumption is if the latest package version is already in the base image, there is no package update and therefore no breakage. For example:
The second run occurred about a day later. I can't tell if this is using a new image, but when I inspected the artifacts from the run. I do see `grub-efi-arm64-bin 2.04-1ubuntu47.4`, which is the latest and the version that [1] tried to upgrade to.
So I guess we generally avoid this by refreshing the ADT base images.
@juliank, ah, I found another detail. This appears to only break when the package is updated in the ADT testbed. My assumption is if the latest package version is already in the base image, there is no package update and therefore no breakage. For example:
[1] older image, fails: https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- bionic/ bionic/ arm64/d/ dpdk/20221027_ 190645_ aae03@/ log.gz /autopkgtest. ubuntu. com/results/ autopkgtest- bionic/ bionic/ arm64/d/ dpdk/20221028_ 185258_ 2a00f@/ log.gz
[2] newer image, passes: https:/
The second run occurred about a day later. I can't tell if this is using a new image, but when I inspected the artifacts from the run. I do see `grub-efi-arm64-bin 2.04-1ubuntu47.4`, which is the latest and the version that [1] tried to upgrade to.
So I guess we generally avoid this by refreshing the ADT base images.