-
Notifications
You must be signed in to change notification settings - Fork 203
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
Broken CI job: apidiff #284
Comments
There is a fix open for
|
thanks for chasing this @MadhavJivrajani |
golang/go#60911 is resolved now 🎉 Created kubernetes/test-infra#30048 |
/close |
@MadhavJivrajani: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The apidiff job is broken since the merge of #243
I don't think its anything to do with the PR itself, but more to do with how apidiff handles things.
I've filed an issue for this with a potential root cause: golang/go#60911
One of 2 can be done here:
utils
to go1.20 and then updatesets
to usecomparable
orapidiff
to be fixed, whatever happens first.Revert add generic sets to utils #243 till we bump to go1.20 or apidiff gets a fix that we can consume (whichever happens first).IMO we should revert for now to ensure the CI is in good shape for when we need to fix something here to mitigate a test flake/failure in something like k/k.Reverting isn't an option since we've already merged the API and
apidiff
will fail on a package level (ref)./cc @logicalhan
/cc @cpanato (in case you have an estimate yet on the go1.20 bumps of release branches)
The text was updated successfully, but these errors were encountered: