Skip to content
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.

Sign up for GitHub

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

Jump to bottom

SQ blocked on verify-codgen #50154

Closed
kow3ns opened this issue Aug 4, 2017 · 4 comments
Closed

SQ blocked on verify-codgen #50154

kow3ns opened this issue Aug 4, 2017 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@kow3ns
Copy link
Member

kow3ns commented Aug 4, 2017

BUG REPORT: The submit queue is broken on head do to errors with hack/verfiy-codegen. It fails after detecting the dif in versioned/clientset with the error message vendor/k8s.io/kube-gen/hack/../test is out of date. Please run hack/update-codegen.sh. Suspect that #49370 may be the trigger if not the cause.

/kind bug
@kow3ns kow3ns added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Aug 4, 2017
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 4, 2017
@kow3ns
Copy link
Member Author

kow3ns commented Aug 4, 2017

@sttts PTAL
/cc

@BenTheElder
Copy link
Member

pull-kubernetes-verify seems to have been passing for a while now for batch jobs at least:
https://prow.k8s.io/?type=batch&job=pull-kubernetes-verify

@kow3ns kow3ns removed the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Aug 4, 2017
@kow3ns
Copy link
Member Author

kow3ns commented Aug 4, 2017

@BenTheElder yeah because other PRs passed through the build queue and #49370 has merge conflict keeping it at bay.

@sttts
Copy link
Contributor

sttts commented Aug 7, 2017

Is this still the case? I just rebased one of my PRs to master and at least unit and verify are green.

@kow3ns kow3ns closed this as completed Aug 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@sttts @BenTheElder @kow3ns @k8s-ci-robot