Skip to content

Sniff out internal failures in another way in CompilationTestHelper. - #4112

Closed
copybara-service[bot] wants to merge 0 commit into
masterfrom
test_567340286
Closed

copybara-service[bot] wants to merge 0 commit into
masterfrom
test_567340286

Conversation

@copybara-service

Copy link
Copy Markdown
Contributor

Sniff out internal failures in another way in CompilationTestHelper.

I had a mysteriously failing test (failing with no diagnostics) which was failing with a NoSuchMethodError in the constructor.

I'm not at all sure this is the right fix!

@Stephan202 Stephan202 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a thought :)

Comment on lines +316 to +319
String stringifiedOutput = outputStream.toString(UTF_8);
assertWithMessage("ErrorProne suffered an internal crash: %s", stringifiedOutput)
.that(stringifiedOutput)
.doesNotContain("An exception has occurred in the compiler");

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do see that there is logic below that inspects the result variable in various cases, but (if I read things correctly) not in all code paths. Looking at its possible values, perhaps it would suffice to check for CMDERR, SYSERR and/or ABNORMAL here?

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.

1 participant