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

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

Closed
wants to merge 0 commits into from

Conversation

copybara-service[bot]
Copy link
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!

Copy link
Contributor

@Stephan202 Stephan202 left a comment

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
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?

@copybara-service copybara-service bot closed this Sep 22, 2023
@copybara-service copybara-service bot deleted the test_567340286 branch September 22, 2023 13:31
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