Bug 1841315: get test pipeline working after unskipping openshift build tests#330
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gabemontero The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@gabemontero: This pull request references Bugzilla bug 1841315, which is invalid:
Comment DetailsIn 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. |
|
/bugzilla refresh |
|
@gabemontero: This pull request references Bugzilla bug 1841315, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
DetailsIn 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. |
|
@gabemontero: Some pull requests linked via external trackers have merged: . The following pull requests linked via external trackers have not merged:
DetailsIn 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. |
So we had to disable https://github.com/openshift/origin/blob/master/test/extended/builds/pipeline_origin_bld.go when https://bugzilla.redhat.com/show_bug.cgi?id=1783530 first arose
That was done via openshift/origin#24304
I noticed that https://bugzilla.redhat.com/show_bug.cgi?id=1783530 was finally marked verified earlier this month as the JDK fix we depended on eventually landed
In creating openshift/origin#25033 the client plugin test using this file was failling.
I reproduced locally, and verified these changes locally.
Once this merges, I'll update the re-enabled test (clean up some of the cleanup stuff) and finish re-enabling the test.
These changes @akram @waveywaves are of course not an exact change from the
jenkins-second-deploymentusage, which I'm assuming you all started to move off of becasue of memory demands, but is close enough for now IMO, and sufficient to get the test re-enablement going.Finally, as a reminder, the pipeline_jenkins_e2e.go tests stayed unskipped during all this.