[jira] [Updated] (KUDU-2820) No JUnit XMLs when running Java dist-test makes for frustrating precommit experience

["Grant Henke (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Henke updated KUDU-2820:
------------------------------
    Issue Type: Improvement  (was: Bug)

> No JUnit XMLs when running Java dist-test makes for frustrating precommit experience
> ------------------------------------------------------------------------------------
>
>                 Key: KUDU-2820
>                 URL: https://issues.apache.org/jira/browse/KUDU-2820
>             Project: Kudu
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 1.10.0
>            Reporter: Adar Dembo
>            Assignee: Grant Henke
>            Priority: Major
>
> When running Java tests in dist-test (as the precommit job does), JUnit XML files aren't generated. That's because normally they're generated by Gradle, but we don't run Gradle in the dist-test slaves; we run JUnit directly.
> As a result, test failures don't propagate back to the Jenkins job, and you have to click through a few links (console output --> link to dist-test job --> filter failures only --> download the artifacts) to figure out what went wrong.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)