-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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/jepsen: failure-logs.tbz archiving is broken #73931
Comments
I think this is on KV honestly (who owns We can probably fix this like this:
or we can get fancy and do something like this (there might be better options)
|
The other thing we could do, now that roachprob is starting get used as a library, is to give the library version of |
This is the second time where I had roachtests being hard to fix because of this behavior (combining stdout with stderr). |
I agree (you are saying that you prefer improving the interface of |
I already added this to the library. For the new (unmerged) jepsen.go, if you only need |
cc @cockroachdb/test-eng |
Jepsen test failure is captured by running tar to stdout and reading other side of ssh pipe. We seem to merge stdout with stderr somewhere along the way so resulting archive file contains garbage if tar issues a warning.
Piece of code that captures archive:
cockroach/pkg/cmd/roachtest/tests/jepsen.go
Lines 283 to 294 in 5e0dac4
Resulting file - see that the data is prefixed with a warning before going to BZ where actual archive starts.
Data could be extracted using
tail -c +68 artifacts/jepsen/bank/majority-ring/run_1/failure-logs.tbz | tar -xjv
in this particular case, but offset may differ depending on errors and get mixed together in worst case.
Jira issue: CRDB-11816
The text was updated successfully, but these errors were encountered: