-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
sql: TestGetUserHashedPasswordTimeout failed #62948
Comments
This only started to fail recently, yet I have not looked into this for the past few months. @rafiss could you perhaps route this to the more appropriate person? |
(sql).TestGetUserHashedPasswordTimeout failed on master@1764c5f7c5642cff6dffe27432c90ab3a3484820:
MoreParameters:
See this test on roachdash |
I bisected this failure to #62581 @yuzefovich would you mind seeing if you can reproduce this result, and if so, investigating further? (the test here uses the internal executor to fetch the hashedPassword, which seems to have been affected in some way by that PR). my bisect was:
|
(sql).TestGetUserHashedPasswordTimeout failed on master@a5f21439d2c455fa78028d54db2cccf6d6f6f7a2:
MoreParameters:
See this test on roachdash |
In the case where the finish() method was called because of a context cancellation, the client might not have observed the context error and instead would have assumed that execution completed successfully. The code now prioritizes the context error if there is one. Fixes cockroachdb#62948 Release note: None
The async and sync implementations were too close to justify two structs. Also, the async behavior of not stopping the writer in case the reader called close wasn't desireable. This commit unifies the implementation. It also ensures that we propagate context errors in all cases triggered by the closure of the done channel. It also makes closing the channel idempotent. Fixes cockroachdb#62948 Release note: None
The async and sync implementations were too close to justify two structs. Also, the async behavior of not stopping the writer in case the reader called close wasn't desireable. This commit unifies the implementation. It also ensures that we propagate context errors in all cases triggered by the closure of the done channel. It also makes closing the channel idempotent. Fixes cockroachdb#62948 Release note: None
(sql).TestGetUserHashedPasswordTimeout failed on master@df07592e26735be7362ef2b815ee163ead00739e:
MoreParameters:
See this test on roachdash |
(sql).TestGetUserHashedPasswordTimeout failed on master@df07592e26735be7362ef2b815ee163ead00739e:
MoreParameters:
See this test on roachdash |
(sql).TestGetUserHashedPasswordTimeout failed on master@df07592e26735be7362ef2b815ee163ead00739e:
MoreParameters:
See this test on roachdash |
63047: sql: temporarily skip flaky test r=yuzefovich a=yuzefovich Addresses: #62948. Release note: None Co-authored-by: Yahor Yuzefovich <[email protected]>
(sql).TestGetUserHashedPasswordTimeout failed on master@6bc054abae5d7e177666e7cc3bc736bee3a99d8b:
More
Parameters:
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: