-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
Data race after update to Gomega 1.14.0 #457
Comments
Thanks @blgm - I think you've uncovered an issue with the new feature... and I may have to end up rolling it back (sigh, globals are terrible). The new feature works by having I'll need to think about it but, sadly, I don't see away around this inherent built-in limitation and will likely have to roll this feature back. |
I think I'll be able to salvage the feature by requiring the user to provide a function that takes in a |
Because of onsi/gomega#457 This reverts commit f822e17.
Just shipped 1.15.0 which should fix this issue. PTAL. |
Hi @onsi, I've updated to 1.15.0, and I don't see the issue any more. Thanks! |
@onsi It seems like this would also be an issue for |
sorry for the delay on my end. Yes |
Worked on Gomega 1.13.0. Data race on update to Gomega 1.14.0, which was "fixed" by downgrading.
The code that encountered the data race was: https://github.com/pivotal-cf/on-demand-service-broker/blob/8db9babdd6b9b533fd4f258d075a6230fb83e681/system_tests/test_helpers/cf_helpers/service.go#L149
It's likely that the reason is this new feature that allows assertions to run in
Eventually()
functions. The code that failed has been doing this (probably incorrectly) for a long time.Log:
It's not immediately obvious to me why this is happing and which code is incorrect. I'm mainly logging this in case someone else immediately sees the issue, or if someone else finds similar issues.
The impact to my team is low because we can just stay on the older version for a while.
The text was updated successfully, but these errors were encountered: