-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ci(dockerd): trigger through chat-ops #3003
base: master
Are you sure you want to change the base?
Conversation
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.
Looks like a good idea to run this on PRs 🎉
For test skipping, woops, most of those should be skipped in the first place I think - I don't think there's any point in trying to get them to work with the moby
exporter in dockerd, since what we're interested in testing are features of the exported images themselves, e.g. annotations need to be attached to containerimage/oci images, oci layout sources need the oci exporter, the timestamps test compares timestamps on built images.
Only one I'm not sure about is the TestCallInfo
: Unimplemented: unknown method Info for service moby.buildkit.v1.Control
- is that moby's buildkit worker not implementing one of the methods? If so, maybe we should have an explicit check that moby's error message is unimplemented, so that we remember to re-enable it once moby re-vendors buildkit?
As it's only on
Also yes I think I will open a PR on moby just to add the implementation and backport to 22.06 and maybe 20.10 (cc @thaJeztah) Edit: BuildKit 0.10.3 on Moby does not have #2725 so we might need to wait for 0.11 or we could backport to v0.10 branch if you are ok with it @tonistiigi? |
Running this on pull requests doesn't really work because the changes a pull request makes are not in the dockerd worker until PR gets merged and vendored into dockerd. |
5d4e938
to
e870da7
Compare
Changed the behavior of the workflow to add a trigger through comment in PR (chat-ops): crazy-max#8
Edit: Actually the checked out ref does not look right. |
Signed-off-by: CrazyMax <[email protected]>
9755e35
to
bd6c34a
Compare
While checking moby/moby#43661 I encounter an issue with our
dockerd
workflow and some recent tests added here fail against this worker.I changed the behavior of the workflow to add a trigger through comment in PR (chat-ops): crazy-max#8
I skip the tests in the meantime but we might be able to make them compatible with dockerd worker (cc @jedevc @tonistiigi @deitch):