@fkorotkov
It looks like the triggered CI workflow from yesterday #54 has not correctly included the transitive dependency of tools in the android-sdk image.
Latest tools digest is sha256:2d9c9176a44b359070057829c9bd9416f1b40618748b24e732ef6fcd61017321
and the android-sdk image uploaded yesterday is using the tools with digest sha256:26895ef68b93d100a657db8eb14ca544eb17791a8bb03dfab6116bb6799004ab
Maybe it is necessary to force pull transitive images before building each image in Cirrus CI?
Probably a temporary solution would be to trigger again the CI for the android repo and then again on the Flutter repo, which conveniently enough has released a hotfix update yesterday 3.10.6
@fkorotkov It looks like the triggered CI workflow from yesterday #54 has not correctly included the transitive dependency of
tools
in theandroid-sdk
image.Latest
tools
digest issha256:2d9c9176a44b359070057829c9bd9416f1b40618748b24e732ef6fcd61017321
and theandroid-sdk
image uploaded yesterday is using thetools
with digestsha256:26895ef68b93d100a657db8eb14ca544eb17791a8bb03dfab6116bb6799004ab
Maybe it is necessary to force pull transitive images before building each image in Cirrus CI?
Probably a temporary solution would be to trigger again the CI for the android repo and then again on the Flutter repo, which conveniently enough has released a hotfix update yesterday 3.10.6
This behavior can be seen in the CI logs:
tools push step
https://cirrus-ci.com/task/4882704085286912?logs=build_tools#L3366
android-sdk build step
https://cirrus-ci.com/task/4882704085286912?logs=build_sdk#L0