-
Notifications
You must be signed in to change notification settings - Fork 152
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
dependency update #315
dependency update #315
Conversation
hack/e2e.sh
Outdated
runTestWithDifferentAddresses "${UDS_NODE}" "${UDS_CONTROLLER}" && | ||
runTestAPIWithCustomTargetPaths "${UDS}" && | ||
runTestWithCustomTargetPaths "${UDS}" "${UDS}" | ||
#runTest "${TCP_SERVER}" "${TCP_CLIENT}" && |
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.
why are all these tests disabled?
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.
Ooops. Because I was manually testing a failing one (caused by the Ginkgo semantic change) and then I forgot to revert that temporary change. Will fix.
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.
Fixed.
Done with `go get -u ./...` The newer Ginkgo change the semantic of Describe() so that the function callback only gets invoked sometime later, which is why we need to rebind the "test" loop variable.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane, pohly 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
No particular reason other than pulling in potential bug fixes.
Does this PR introduce a user-facing change?: