Skip to content
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: Fix error reporting in kv50 test #41480

Closed
wants to merge 1 commit into from

Conversation

bdarnell
Copy link
Contributor

@bdarnell bdarnell commented Oct 9, 2019

When one thread in a monitor fatals and another returns an error, the
fatal is the one that gets reported, even if it's an unhelpful
"signal: killed" from a cancelled process that was caused by a
previously returned error. Whenever any thread returns errors, they
all should, by using RunE instead of Run, etc. This is probably a much
more widespread problem in the roachtests, but for now I'm only fixing
this one which is causing opaque failures in #40359

Release note: None

When one thread in a monitor fatals and another returns an error, the
fatal is the one that gets reported, even if it's an unhelpful
"signal: killed" from a cancelled process that was caused by a
previously returned error. Whenever any thread returns errors, they
all should, by using RunE instead of Run, etc. This is probably a much
more widespread problem in the roachtests, but for now I'm only fixing
this one which is causing opaque failures in cockroachdb#40359

Release note: None
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@nvanbenschoten
Copy link
Member

I think this is a duplicate of #41106, which I've been struggling to get merged. I'll give it another push.

@bdarnell bdarnell closed this Oct 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants