Closed akram closed 3 years ago
@akram: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh
.
/retitle Bug 1866789: Remove problematic upstream client plugin test
@akram: This pull request references Bugzilla bug 1866789, 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.
/assign gabemontero
/test unit
@akram .... do you envision ever updating jenkins client plugin for 3.11 moving forward?
The client plugin e2e's I added in https://github.com/openshift/release/tree/master/ci-operator/jobs/openshift/jenkins-client-plugin technically only validate against OCP 4.x
I'm fine with merging this to unblock say jenkins core/dependent plugin security fixes, but IF you ever updating the client plugin on 3.11 (I personally think you should NOT because 3.11 is EOL .... only consider it if some major security flaw is identified), then either you guys have to validate it manually and hope for the best, or you create a 3.11 branch for client plugin based on whatever commit level is shipped there and create 3.11 versions of the plugin e2e's like what you see at https://github.com/openshift/release/tree/master/ci-operator/jobs/openshift/origin
Again, I think that is overkill, but want to make sure you are fully aware of the implications of removing this test here.
for extended_builds there are panic on many kubectl calls:
error running &{/usr/bin/kubectl [kubectl --server=https://internal-api.ci-op-2lh6q0il-7a04a.origin-ci-int-gce.dev.rhcloud.com:8443 --kubeconfig=/tmp/admin.kubeconfig exec --namespace=e2e-tests-persistent-local-volumes-test-9lqtf security-context-98786517-d7f4-11ea-a277-0a580a830036 -- /bin/sh -c cat /mnt/volume1/test-file] [] <nil> runtime/cgo: pthread_create failed: Resource temporarily unavailable
SIGABRT: abort
PC=0x7f04c93e8387 m=9 sigcode=18446744073709551610
looks like a flake
/test extended_builds
/test e2e-gcp /test unit
@akram .... do you envision ever updating jenkins client plugin for 3.11 moving forward?
The client plugin e2e's I added in https://github.com/openshift/release/tree/master/ci-operator/jobs/openshift/jenkins-client-plugin technically only validate against OCP 4.x
I'm fine with merging this to unblock say jenkins core/dependent plugin security fixes, but IF you ever updating the client plugin on 3.11 (I personally think you should NOT because 3.11 is EOL .... only consider it if some major security flaw is identified), then either you guys have to validate it manually and hope for the best, or you create a 3.11 branch for client plugin based on whatever commit level is shipped there and create 3.11 versions of the plugin e2e's like what you see at https://github.com/openshift/release/tree/master/ci-operator/jobs/openshift/origin
Again, I think that is overkill, but want to make sure you are fully aware of the implications of removing this test here.
@gabemontero indeed, we will do the validations manually. The process gets more and more complex for us to deliver fixes for cve's. We cannot afford to have distinct branches for this plugins of for tests now.
/lgtm
I'm only a reviewer in 3.11 @akram
we'll need an approver from the OWNERS file
/assign @bparees
/approve
/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.
/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.
/hold
/test unit
unit
task now failing with:
[INFO] hack/build-go.sh exited with code 0 after 00h 00m 05s
FAIL: github.com/openshift/origin/pkg/build/builder TestDockerfilePath 20ms
FAIL: github.com/openshift/origin/pkg/build/builder TestDockerfileFromScratch 10ms
FAIL: github.com/openshift/origin/pkg/build/builder TestDockerBuildError 0s
FAIL: github.com/openshift/origin/pkg/build/builder TestPushError 0s
FAIL: github.com/openshift/origin/pkg/build/builder TestGetStrategyError 0s
Only these 5 tests related to Docker fails. Another empty commit PR seems to show the same error. A previous test was failing with:
FAIL: github.com/openshift/origin/pkg/build/builder TestDockerfilePath 10ms
FAIL: github.com/openshift/origin/pkg/build/builder TestDockerfileFromScratch 0s
FAIL: github.com/openshift/origin/pkg/build/builder TestDockerBuildError 0s
FAIL: github.com/openshift/origin/pkg/build/builder TestPushError 0s
FAIL: github.com/openshift/origin/pkg/build/builder TestGetStrategyError 0s
FAIL: github.com/openshift/origin/pkg/network/node TestEgressVXLANMonitor 10ms
Re-running all the others .
/retest
/retest
RHEL repository flake:
leveldb-1.12.0-5.el7.1.x86_64: [Errno 256] No more mirrors to try.
/test e2e-gcp
/retest
/test images
flake again and over again
2:python-rados-12.2.11-0.el7.x86_64: [Errno 256] No more mirrors to try.
/test e2e-gcp
/retest
/retest
/hold cancel
/retest
/retest
/retest
@akram: The following test failed, say /retest
to rerun all failed tests:
Test name | Commit | Details | Rerun command |
---|---|---|---|
ci/openshift-jenkins/extended_builds | 4fe5abe4af2f8cdb9662476d78dc4b36503bb892 | link | /test extended_builds |
Full PR test history. Your PR dashboard.
/uncc
Ignore me. /test extended_builds
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: akram, bparees, gabemontero
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test extended_builds
/test extended_builds
@waveywaves @jkhelil fyi