restructure jenkins ext tests for origin/build speed up #21504
Conversation
openshift-ci-robot
added
the
size/XXL
|
/test extended_builds |
|
/refresh |
|
ok how the hell do i get the extended builds job scheduled ...grepping on openshift/release the command appears to be /test extended_builds |
|
/test e2e-gcp-builds but it's already running. extended-builds isn't a thing anymore. |
|
e2e-aws failure: more IP pain: |
|
/retest e2e-aws |
|
@gabemontero as i'm unlikely to have time to give this a solid review, please have @adambkaplan give it a second set of eyes, but basically i trust you, if you think this is giving us the coverage we need and it's speeding up (or parallelizing) the execution, i'm fine with it. /approve |
openshift-ci-robot
added
the
approved
|
/assign @adambkaplan |
|
sounds good @bparees |
|
OK
retesting to see about consistency |
|
/retest |
|
/lgtm |
|
@smarterclayton fyi, see if this helps w/ the build test time concerns you had after it merges. |
|
@smarterclayton - while the removal of Is there some special focus string we can apply to the tests that leverage all the actual samples like mongodb, etc. so they don't get run in the conformance test? The intent of this PR is to run those in the openshift/jenkins e2e ... We only want to run our optimized test samples (that circumvent all these slow samples) in |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
gabemontero
force-pushed
the
jenkins-ext-tst
branch
from
66ad3e7
to
6ade13f
Compare
|
@bparees and @smarterclayton got us sorted out in forum-devex ... PR updated to exclude jenkins tests from conformance e2e-gcp |
|
@gabemontero once you confirm the test isn't running in gcp let me know and i'll lgtm it |
|
/test integration |
|
|
|
/lgtm
…On Mon, Nov 19, 2018 at 5:07 PM, Gabe Montero ***@***.***> wrote:
e2e-gcp run https://openshift-gce-devel.appspot.com/build/origin-ci-
test/pr-logs/pull/21504/pull-ci-openshift-origin-master-e2e-gcp/1965
completed successfully @bparees <https://github.com/bparees> and the
jenkins tests are correctly omitted
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21504 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEvl3lwFRbB2xnjRiLRI9Vhi13T5ywacks5uwyuJgaJpZM4YgYOn>
.
--
Ben Parees | OpenShift
|
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
for several days now the e2e-gcp still is correct in that none of the jenkins tests are in it the failures fall across several components in that time ... in the build space, they are generally registry / docker related: |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
9 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
Clayton uncovered a dockerhub spat of flakiness that mos likely explains the e2e-gcp build failures I noted in #21504 (comment) They have appeared to addressed that and it is no longer occurring. Just a couple of networking items in the last run. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
12 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
a restructure of the jenkins pipeline tests given @smarterclayton 's complaints on the time spent
Rationale
openshift pipeline buildwhich remain in both filesmvn --versionandsh exit 0/assign @bparees