-
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
sql/logictest: TestLogic failed #83367
Comments
sql/logictest.TestLogic failed with artifacts on master @ b47dc374417fe4ba83570784040da5650238b30e:
Same failure on other branches
|
sql/logictest.TestLogic failed with artifacts on master @ a611410e3babe97a14152381b89060e1bafa2e27:
Same failure on other branches
|
This fails only on
|
sql/logictest.TestLogic failed with artifacts on master @ 7f8fef4c3f24ec2b6f9a3db1eb38756da68b3d5a:
Same failure on other branches
|
sql/logictest.TestLogic failed with artifacts on master @ ac11a55499120ffd33016feebc47b4ed43a21007:
Same failure on other branches
|
83386: batcheval: handle MVCC range tombstones in `RefreshRange` r=aliher1911 a=erikgrinaker This patch add handling of MVCC range tombstones in `RefreshRange`, by erroring on them as a committed value. Resolves #83383. Release note: None 83562: rowexec: fix recent bug of using nil context r=yuzefovich a=yuzefovich In e7e724e we moved the creation of a monitor for the streamer's disk usage into the constructor of the join reader but forgot to update the context used during that operation. The thing is that the context on the processors is only set in `Start` meaning it is `nil` in the construct of the processor. This commit fixes the issue. Fixes: #83367 Release note: None Co-authored-by: Erik Grinaker <grinaker@cockroachlabs.com> Co-authored-by: Yahor Yuzefovich <yahor@cockroachlabs.com>
sql/logictest.TestLogic failed with artifacts on master @ fc7ae339c3f85ad2a2b28643e47d7c20768fe237:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-17025
The text was updated successfully, but these errors were encountered: