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
HDDS-2265. integration.sh may report false negative #1608
Conversation
/label ozone |
💔 -1 overall
This message was automatically generated. |
@elek please review (let me know if I should retest until we hit the case when integration test gets killed) |
@@ -45,6 +45,11 @@ grep -A1 'Crashed tests' "${REPORT_DIR}/output.log" \ | |||
| cut -f2- -d' ' \ | |||
| sort -u >> "${REPORT_DIR}/summary.txt" | |||
|
|||
## Check if Maven was killed | |||
if grep -q 'Killed.* mvn .* test ' "${REPORT_DIR}/output.log"; then |
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.
So we are presuming that Killed will never be used by a test? :) I am fine with that.
+1. LGTM.
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 Thanks the contribution @adoroszlai
Later we can improve it to collect all of the test names which are failing, but it's good enough to show the "JVM crash" type failures.
Thanks @anuengineer and @elek for reviewing, and @elek for committing it. |
What changes were proposed in this pull request?
Check if Maven was killed during test run (observable in integration test runs). If so, mention it in
summary.txt
. Non-emptysummary.txt
is handled as "failure".https://issues.apache.org/jira/browse/HDDS-2265
How was this patch tested?
Tested both positive and negative case:
summary.txt
remains emptymvn
process, verified thatsummary.txt
contains the expected line