-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore(deps): Updated to ginkgo v2 #2459
Conversation
Changes look good, but somehow it's broken the redis tests so will need some investigation as to why those are broken now |
I'll have a look this evening |
@tuunit any idea? I've been going around in circles for a couple of hours. A fresh pair of (more experienced) eyes would help. |
Currently showing
Which looks like it should be fairly straightforward, AfterSuite cannot be nested inside another container |
Should be |
@kvanzuijlen @JoelSpeed I fixed the Ginkgo issues :) |
Indeed this was one of the issues. Ginkgo v1 didn't really enforce that Furthermore, the execution order seems to have changed slightly which causes issues with the miniredis teardown. Therefore I separated the redis store tests into two specs. One for the miniredis configure with TLS and one without. |
This pull request has been inactive for 60 days. If the pull request is still relevant please comment to re-activate the pull request. If no action is taken within 7 days, the pull request will be marked closed. |
* chore(deps): Updated to ginkgo v2 * fix basic auth test suite cleanup * fix redis store tests * add changelog entry --------- Co-authored-by: Jan Larwig <[email protected]>
Description
Updated ginkgo to v2
Motivation and Context
Ginkgo was outdated
How Has This Been Tested?
Checklist:
Ran tests locally.
I don't think this change requires a changelog entry since only _test.go files were changed