-
Notifications
You must be signed in to change notification settings - Fork 9
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
test_load_balancer_keep_last_elm
test fails occasionally
#1395
Comments
I have concerns about this chunk of code:
I'm concerned that I may have borked GreedyLB when I removed temporary IDs from the load balancers. Can @lifflander or @PhilMiller take a look and let me know how they think this was supposed to work? |
@lifflander and I discussed this and decided this chunk of code is correct. |
This is a lot more difficult to reproduce on my Mac than I expected given how frequently I feel like it shows up on CI. It shows up for me on Mac best with 4 ranks. Maybe it would show up more frequently in Docker. You can run only this GreedyLB test by running something like below, but I recommend redirecting the output to file.
|
@nlslatt I actually just commented out the other LBs to get it to reproduce easily, but I should have thought of that. |
So I've enabled address sanitizer and it comes out clean even when it fails. However, I was able to print the data and it indeed looks corrupted:
|
Describe the bug
vt:*/TestLoadBalancer.test_load_balancer_keep_last_elm/*_proc_2
test fails randomly in CI.This can be reproduced in local using:
ctest -R TestLoadBalancer.test_load_balancer_keep_last_elm --output-on-failure --repeat-until-fail 100
Assertion:
Backtrace:
full output
The text was updated successfully, but these errors were encountered: