-
Notifications
You must be signed in to change notification settings - Fork 38.7k
ci: Add missing docker.io prefix for native tasks to CI_IMAGE_NAME_TAG #28330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
Does it make sense to be explicit about an architecture: |
Why? and How? The architecture is |
Wouldn't that just defeat the point of this change? |
|
Before #21652, it was obvious that the fuzzers task is executed on a |
|
#21652 should be unrelated to any CI changes, because it didn't touch the To find out the architecture, you can look at the logs. For example, the |
It is related because now it is possible to change worker architectures.
Another run might use a worker with arm64 architecture (potentially), no? |
The CI system was already being used on x86_64 and aarch64 long before that PR was merged. Hopefully we'll even have a third architecture soon. |
I mean, non-intentional change, for example, by an error. |
Correct, but then that seems unrelated to this pull request here. |
|
To clarify, this pull request fixes a bug that exists since |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK fab7f5c.
FWIW, on my machines the following strings work:
x86_64hardware:'docker.io/amd64/debian:bookworm'arm64hardware:'docker.io/arm64v8/debian:bookworm'
…s to CI_IMAGE_NAME_TAG
Currently, the CI system may pick the wrong (non-native) architecture due to the missing prefix.
For example, assuming the CI_IMAGE_NAME_TAG is
debian:bookwormand the user has previously pulled an s390x image:Now,
debian:bookwormwill refer to the same image:However,
docker.io/debian:bookwormworks fine: