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
[SPARK-38723][SS][TEST][FOLLOWUP] Deflake the newly added test in QueryExecutionErrorsSuite #43565
Conversation
cc @HeartSaVioR |
@HyukjinKwon Also the test should have failed in previous CI. In the checkError method we check if parameters match when the exception has parameter
So it should have thrown as:
The first is the parameter in the error itself, the second is empty because previously no parameter was passed in that checkError. So it should have been checked out in CI. Could this be a build issue (like the test wasn't ran at all..? |
exceptions.map { e => | ||
if (e.isDefined) { | ||
checkError( | ||
e.get, | ||
errorClass = "CONCURRENT_QUERY", | ||
sqlState = Some("0A000") | ||
sqlState = Some("0A000"), | ||
parameters = e.get.getMessageParameters.asScala.toMap | ||
) | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you simplify this?
exceptions.flatten.foreach { e =>
checkError(
e,
errorClass = "CONCURRENT_QUERY",
sqlState = Some("0A000"),
parameters = e.getMessageParameters.asScala.toMap
)
}
Looks like the test failure in CI is irrelevant. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
@MaxGekk Please either merge this or let me know once you're OK with the change. Thanks! |
+1, LGTM. Merging to master. |
What changes were proposed in this pull request?
The newly added test in 7d7afb0 could be flaky, this change deflakes it. Details see comments.
Why are the changes needed?
Deflaky
Does this PR introduce any user-facing change?
Test only change
How was this patch tested?
Test only change
Was this patch authored or co-authored using generative AI tooling?
No