zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1363) Categorise unit tests by 'test-commit', 'full-test' etc
Date Wed, 27 Sep 2017 20:06:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183176#comment-16183176
] 

Hadoop QA commented on ZOOKEEPER-1363:
--------------------------------------

-1 overall.  GitHub Pull Request  Build
      

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 13 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 3.0.1) warnings.

    -1 release audit.  The applied patch generated 5 release audit warnings (more than the
trunk's current 0 warnings).

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1047//testReport/
Release audit warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1047//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1047//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1047//console

This message is automatically generated.

> Categorise unit tests by 'test-commit', 'full-test' etc
> -------------------------------------------------------
>
>                 Key: ZOOKEEPER-1363
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1363
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: build, tests
>            Reporter: Henry Robinson
>            Assignee: Mark Fenes
>              Labels: newbie
>
> As discussed on the list, it would be good to split the Java test suite into categories
so that it's easy to run a small set of unit tests against a patch, and to leave Jenkins to
run the full suite of stress tests etc. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message