-
Notifications
You must be signed in to change notification settings - Fork 351
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 TestTrafficSegmentSplit #2665
Comments
https://github.com/zalando/skipper/actions/runs/8962466724/job/24611376295?pr=3060
|
master build fails:
|
Another occurrence at #3326 see #3326 (comment) |
I've already tried to fix it by #2423 |
I think the way TrafficSegment works makes this test to have a non-zero chance to fail. $ go test ./predicates/traffic/ -run=TestTrafficSegmentSplit -count=1000 -failfast -trimpath
--- FAIL: TestTrafficSegmentSplit (0.36s)
segment_test.go:164: Response codes: map[200:5131 201:2991 202:1878]
segment_test.go:168:
Error Trace: github.com/zalando/skipper/predicates/traffic/segment_test.go:93
github.com/zalando/skipper/predicates/traffic/segment_test.go:168
Error: Max difference between 2000 and 1878 allowed is 120, but difference was 122
Test: TestTrafficSegmentSplit
FAIL
FAIL github.com/zalando/skipper/predicates/traffic 9.645s
FAIL There is an interesting proposal to deal with flaky tests in stdlib golang/go#62244 but its not implemented yet. |
Use fixed random sequence to deflake TestTrafficSegmentSplit. Fixes #2665 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Created #3330 that uses fixed random sequence to deflake this test. |
Use fixed random sequence to deflake TestTrafficSegmentSplit. Fixes #2665 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Use fixed random sequence to deflake TestTrafficSegmentSplit. Fixes #2665 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Use fixed random sequence to deflake TestTrafficSegmentSplit. Fixes #2665 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
The text was updated successfully, but these errors were encountered: