-
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_upsert failing due to hardware overload #119907
Comments
I'm guessing this should be fixed by #119953 |
Hi @yuzefovich, that PR has nothing to do with this failure. That PR is about |
Oops, misclick. Still, this failure doesn't really seem actionable to me, here is what we have in logs:
Table 145 is dropped right before we create I have not seen this failure mode on logic tests in TeamCity, so I'm inclined to assume it's something about EngFlow environment. |
|
Maybe just due to metamorphic settings making things slow? |
We're seeing a few of these "context canceled" failures in the last few days. So it seems like there's some recent change to code or infrastructure that is causing this. |
120417: logictest: move large upsert tests to non-metamorphic file r=yuzefovich a=yuzefovich We've seen a few suspicious failures around a couple of test cases in the `upsert` file that use large number of rows, so this commit moves them into the non-metamorphic file in hopes of preventing flakes. Additionally, I'm guessing these test cases were the reason for recently added skip under race, so that is removed too. Informs: #119907. Epic: None Release note: None Co-authored-by: Yahor Yuzefovich <[email protected]>
It seems like this is a duplicate of #120395, correct? |
I think so, closing as a dup of #120395 |
pkg/sql/logictest/tests/local-vec-off/local-vec-off_test.TestLogic_upsert failed on master @ bf013ea0a5311726e65d37e8f047ce39ea2d5f10:
Parameters:
attempt=1
run=29
shard=45
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-36379
The text was updated successfully, but these errors were encountered: