-
Notifications
You must be signed in to change notification settings - Fork 465
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
Flaky test: ratelimit_legacy_test.go:157: TestServiceLegacy #256
Comments
sunjayBhatia
added a commit
to sunjayBhatia/ratelimit
that referenced
this issue
May 25, 2021
User deferred barrier.signal() so panic definitely occurs before we continue on in test. Config reload uses recover() and increments config load counter, tests were failing to see config load error counter increment. Fixes: envoyproxy#256 Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
mattklein123
pushed a commit
that referenced
this issue
May 25, 2021
User deferred barrier.signal() so panic definitely occurs before we continue on in test. Config reload uses recover() and increments config load counter, tests were failing to see config load error counter increment. Fixes: #256 Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
storozhukBM
pushed a commit
to storozhukBM/ratelimit-1
that referenced
this issue
May 28, 2021
User deferred barrier.signal() so panic definitely occurs before we continue on in test. Config reload uses recover() and increments config load counter, tests were failing to see config load error counter increment. Fixes: envoyproxy#256 Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com> Signed-off-by: bstorozhuk <storozhuk.b.m@gmail.com>
zdmytriv
pushed a commit
to verygoodsecurity/ratelimit
that referenced
this issue
Aug 2, 2021
User deferred barrier.signal() so panic definitely occurs before we continue on in test. Config reload uses recover() and increments config load counter, tests were failing to see config load error counter increment. Fixes: envoyproxy#256 Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
timcovar
pushed a commit
to goatapp/ratelimit
that referenced
this issue
Jan 16, 2024
User deferred barrier.signal() so panic definitely occurs before we continue on in test. Config reload uses recover() and increments config load counter, tests were failing to see config load error counter increment. Fixes: envoyproxy#256 Signed-off-by: Sunjay Bhatia <sunjayb@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failing in CI but passes when I run locally
See runs:
Test:
ratelimit/test/service/ratelimit_legacy_test.go
Line 157 in bc0e9fa
The text was updated successfully, but these errors were encountered: