-
Notifications
You must be signed in to change notification settings - Fork 4.7k
re-enable jenkins client plugin ext tests #19465
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
re-enable jenkins client plugin ext tests #19465
Conversation
change lgtm but looks like it is still failing. |
Yeah same failure as before. The only explanation that comes to my mind is back to a timing thing on the I just instantiated that template manually and was able to get the dc with the same name:
Going the update the pipeline job in the client plugin repo and add a delay ... maybe some debug. |
Here is the precise error in the pipeline run:
|
Yep and re-confirmed, the vanilla image and that portion of the job runs for me when running locally:
|
ok ...sorted it out... another client plugin PR / image update needed Did verify ALL the client plugin ext tests locally this time. Let's hope there are no more openshift/origin breaking changes before I get the stuff merged / updated |
/retest |
the ext builds test is passing now @bparees with the latest client plugin / image update |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, gabemontero The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
OK, we are now getting the same jenkins_plugin.go error that was in the overnight run:
Either there is a regression in that the ext test framework cleans up namespaces, or a new restriction has been put in place. @coreydaley - as ext test babysitter, will you have cycles to check out recent commits to openshift/master, poll usual suspects about this? If not, I'll circle back to it after some bug curation I need to do .... as a last resort, we can disable those old plugin tests in the interim. |
/retest |
Unit test failure:
@openshift/sig-storage fyi ^^ |
The failure could be because of kubernetes/kubernetes#62827 we may have to backport it (I have not tested it) |
ok thanks @gnufied on the test this PR is interested in, @bparees / @coreydaley , either the namespace cleanup got addressed, it is is just a flake that is hiding for the moment, as extended builds test passed. |
/retest |
xref : openshift/origin#19465 Origin-commit: f320c6dae53c0b459ef8420654baf66cbe8eb63a
@openshift/sig-developer-experience fyi
(there may be some timing issues to sort out with the test pipeline in the client-plugin repo, or an as yet tbd issue accessing oapi objects, with recent 3.10 changes ... let's see what happens)