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: fails to terminate cleanly when device full #32384
Comments
In addition to not posting an issue, we're also not marking the tests that were uncompleted as failures in teamcity. Our Go test output parser does this. |
Well that's not good. Will an external poster be able to post if the disk is full? |
Yes, with the external poster it would see Go test output and fail all tests that weren't explicitly terminated. That's the "test ended in panic" message we see in such cases. It would not, however, fail tests that weren't ever mentioned in the logs. To work around that, roachtest should emit a header for all tests that it's going to run and immediately pause them via |
We have marked this issue as stale because it has been inactive for |
still relevant |
We have marked this issue as stale because it has been inactive for |
I was looking at the history of restore2TB/nodes=10 and wondered why it had a relatively fast passing result on release-2.1. Looking at the logs, I found that
roachtest
had shot itself since it ran out of space.For these runs,
roachtest
itself is in charge of posting issues. This is problematic because nobody watches the watchman. Regarding the discussion about having roachtest be in charge of posting its issues in more places, I think we may want to take the opposite route and not have it post anything any more.Epic CRDB-10428
Jira issue: CRDB-4752
The text was updated successfully, but these errors were encountered: