Closed akalenyu closed 3 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
/test pull-cdi-goveralls
@mhenriks @awels I am not sure what the second failure is about though: https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_containerized-data-importer/3336/pull-cdi-goveralls/1809334945819136000
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from akalenyu. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
@akalenyu: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-cdi-goveralls | 0ec536cbe654d467d1dd549869de1717b1ad0eb1 | link | false | /test pull-cdi-goveralls |
/test pull-cdi-goveralls
@mhenriks @awels I am not sure what the second failure is about though: https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_containerized-data-importer/3336/pull-cdi-goveralls/1809334945819136000
TBH I think the time package is rooted much further in the cert helpers so dropping this for now https://github.com/kubevirt/project-infra/pull/3512 to alleviate
/close
@akalenyu: Closed this PR.
This is flaking very frequently on the goveralls lane; Probably has to do with the kubevirt-prow-control-plane workload cluster in CI, anyway, we have no business testing real time.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes #Special notes for your reviewer:
Release note: