-
Notifications
You must be signed in to change notification settings - Fork 453
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
Switch to ginkgo/v2 #910
Switch to ginkgo/v2 #910
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert 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 |
c360232
to
218925e
Compare
b7789c3
to
073ce43
Compare
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@feiskyer PTAL |
FYI... containerd/containerd#6894 Note the comment that critest --ginkgo.focus="HostIpc" --ginkgo.skip="HostIpc is true" works but add --parallel=2 and it fails to focus or skip.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Following kubernetes-sigs/cri-tools#910 the Ginkgo reporters are left configured with default settings and thus do not generate a JUnit report file unless we explicitly pass a path for the outfile in the Windows workflow when calling critest.exe. Signed-off-by: Nashwan Azhari <nazhari@cloudbasesolutions.com>
Following kubernetes-sigs/cri-tools#910 the Ginkgo reporters are left configured with default settings and thus do not generate a JUnit report file unless we explicitly pass a path for the outfile in the Windows workflow when calling critest.exe. Signed-off-by: Nashwan Azhari <nazhari@cloudbasesolutions.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
Ginkgo v2 has been released since a while and we should upgrade to the new dependency.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?