-
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
roachtest: schemachange/index/tpcc/w=1000 failed #76230
Comments
@ajwerner to put artifacts in the cloud for future investigation. |
Artifacts are here for posterity: https://drive.google.com/file/d/1BxQj65a1_T1_CEBibQeF_r1_sYvhlKyu/view?usp=sharing |
So, the node dies, no sign of an oom, no heap profile, no panic, nothing. What in the world! The VM doesn't die, just the process. I visualized the timeseries data, nothing gives. I'm going to say we have no clue. |
I should add that the exit file does say
We know that 128+9 = 137 so it was a SIGKILL. :/ Not from the oomkiller though. Who killed my process! |
Oh, I found something interesting in journalctl:
|
Given it seems like a broken tcp connection from teamcity, I'm going to close this as unactionable. |
roachtest.schemachange/index/tpcc/w=1000 failed with artifacts on release-21.2 @ 79c1f34aa3c91977ed6784338d7383931733d0b6:
Reproduce
See: roachtest README
Same failure on other branches
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: