You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2019/05/08 19:58:00 UTC

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

Adar Dembo created KUDU-2820:
--------------------------------

             Summary: 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: Bug
          Components: test
    Affects Versions: 1.10.0
            Reporter: Adar Dembo


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
(v7.6.3#76005)