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.

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

Swagger spec is causing failures on ci/openshift-jenkins/origin/verify job #16720

Closed
abstractj opened this issue Oct 6, 2017 · 4 comments
Closed
Assignees
Labels
component/internal-tools kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2

Comments

@abstractj
Copy link
Contributor

While updating my PR #16034. I found this at the logs: https://s3.amazonaws.com/archive.travis-ci.org/jobs/284191227/log.txt?X-Amz-Expires=30&X-Amz-Date=20171006T130447Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20171006/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=b42bd12e348a38887ad53b47874173128c5ebc7b0606e42c43233b311a1ae9f1

[ERROR] PID 1: hack/lib/cmd.sh:241: `return "${return_code}"` exited with status 1.
... skipping 4 lines ...
[ERROR] hack/verify-generated-completions.sh exited with code 1 after 00h 00m 27s
... skipping 102 lines ...
[FATAL] Swagger spec is out of date. Please run hack/update-generated-swagger-spec.sh:
[FATAL] diff -Naupr -I 'Auto generated by' /go/src/github.com/openshift/origin/api/swagger-spec/api-v1.json /go/src/github.com/openshift/origin/_output/verify-generated-swagger-spec/api/swagger-spec/api-v1.json
[FATAL] --- /go/src/github.com/openshift/origin/api/swagger-spec/api-v1.json	2017-10-06 11:38:40.000000000 +0000
[FATAL] +++ /go/src/github.com/openshift/origin/_output/verify-generated-swagger-spec/api/swagger-spec/api-v1.json	2017-10-06 11:43:11.432960084 +0000

This looks completely unrelated with my changes, because I haven't changed anything at the Swagger Spec

@abstractj abstractj added kind/bug Categorizes issue or PR as related to a bug. priority/P0 labels Oct 6, 2017
@simo5
Copy link
Contributor

simo5 commented Oct 6, 2017

@stevekuznetsov was this perchance a run on the new pipeline tests ?

@stevekuznetsov
Copy link
Contributor

This was on the new pipeline. Not critical.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 22, 2018
@stevekuznetsov
Copy link
Contributor

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/internal-tools kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2
Projects
None yet
Development

No branches or pull requests

7 participants