-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
teamcity: failed tests on master: testrace/TestHeartbeatHealth, test/TestHeartbeatHealth #27340
Comments
@m-schneider, could you take a look at this? Likely caused by your recent PR. |
I took a look, it looks like the first breakage was June 13th and I could reproduce it before my PR. It looks like there's a race where the error gets set here Lines 545 to 634 in 98b99aa
instead of Lines 221 to 226 in 98b99aa
I think both seem valid. |
I think the test needs to change. ConnHealth isn't supposed to work with strings that aren't of the form I think the simplest way to do this is to create three listeners with net.Listen() and don't do anything with them, but use their addresses. Hopefully that will all clean up nicely if you close the listener at the end of the test. |
This test was sending strings to ConnHealth not of the form host:port, which was being validated asynchronously and sometimes caused that validation error to be recieved before an ErrNotHeartbeated error. Now we'll use addresses of the correct form, so we should always receive the ErrNotHeartbeated error. Close cockroachdb#27340 Release note: None
This test was sending strings to ConnHealth not of the form host:port, which was being validated asynchronously and sometimes caused that validation error to be recieved before an ErrNotHeartbeated error. Now we'll use addresses of the correct form, so we should always receive the ErrNotHeartbeated error. Close cockroachdb#27340 Release note: None
27408: rpc: fix TestHeartbeatHealth r=m-schneider a=m-schneider This test was sending strings to ConnHealth not of the form host:port, which was being validated asynchronously and sometimes caused that validation error to be recieved before an ErrNotHeartbeated error. Now we'll use addresses of the correct form, so we should always receive the ErrNotHeartbeated error. Close #27340 Release note: None Co-authored-by: Masha Schneider <[email protected]>
The following tests appear to have failed:
#771008:
Please assign, take a look and update the issue accordingly.
The text was updated successfully, but these errors were encountered: