[
https://issues.apache.org/jira/browse/HADOOP-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HADOOP-11746:
--------------------------------------
Release Note:
<!-- markdown -->
* test-patch.sh now has new output that is different than the previous versions
* test-patch.sh is now pluggable via the test-patch.d directory, with
checkstyle and shellcheck tests included
* JIRA comments now use much more markup to improve readability
* test-patch.sh now supports either a file name, a URL, or a JIRA issue as
input in developer mode
* If part of the patch testing code is changed, test-patch.sh will now attempt
to re-executing itself using the new version.
* Some logic to try and reduce the amount of unnecessary tests. For example,
patches that only modify markdown should not run the Java compilation tests.
* Plugins for checkstyle, shellcheck, and whitespace now execute as necessary.
* New test code for mvn site
* A breakdown of the times needed to execute certain blocks as well as a total
runtime is now reported to assist in fixing long running tests and optimize the
entire process.
* Several new options
* --resetrepo will put test-patch.sh in destructive mode, similar to a normal
Jenkins run
* --testlist allows one to provide a comma delimited list of test subsystems
to forcibly execute
* --modulelist to provide a comma delimited list of module tests to execute
in addition to the ones that are automatically detected
* --offline mode to attempt to stop connecting to the Internet for certain
operations
* test-patch.sh now defaults to the POSIX equivalents on Solaris and
Illumos-based operating systems
* shelldocs.py may be used to generate test-patch.sh API information
* FindBugs output is now listed on the JIRA comment
* lots of general code cleanup, including attempts to remove any local state
files to reduce potential race conditions
* Some logic to determine if a patch is for a given major branch using several
strategies as well as a particular git ref (using git+ref as part of the name).
* Some logic to determine if a patch references a particular JIRA issue.
* Unit tests are only flagged as necessary with native or Java code, since
Hadoop has no framework in place yet for other types of unit tests.
* test-patch now exits with a failure status if problems arise trying to do git
checkouts. Previously the exit code was success.
was:
* test-patch.sh now has new output that is different than the previous versions
* test-patch.sh is now pluggable via the test-patch.d directory, with
checkstyle and shellcheck tests included
* JIRA comments now use much more markup to improve readability
* test-patch.sh now supports either a file name, a URL, or a JIRA issue as
input in developer mode
* If part of the patch testing code is changed, test-patch.sh will now attempt
to re-executing itself using the new version.
* Some logic to try and reduce the amount of unnecessary tests. For example,
patches that only modify markdown should not run the Java compilation tests.
* Plugins for checkstyle, shellcheck, and whitespace now execute as necessary.
* New test code for mvn site
* A breakdown of the times needed to execute certain blocks as well as a total
runtime is now reported to assist in fixing long running tests and optimize the
entire process.
* Several new options
* --resetrepo will put test-patch.sh in destructive mode, similar to a normal
Jenkins run
* --testlist allows one to provide a comma delimited list of test subsystems
to forcibly execute
* --modulelist to provide a comma delimited list of module tests to execute
in addition to the ones that are automatically detected
* --offline mode to attempt to stop connecting to the Internet for certain
operations
* test-patch.sh now defaults to the POSIX equivalents on Solaris and
Illumos-based operating systems
* shelldocs.py may be used to generate test-patch.sh API information
* FindBugs output is now listed on the JIRA comment
* lots of general code cleanup, including attempts to remove any local state
files to reduce potential race conditions
* Some logic to determine if a patch is for a given major branch using several
strategies as well as a particular git ref (using git+ref as part of the name).
* Some logic to determine if a patch references a particular JIRA issue.
* Unit tests are only flagged as necessary with native or Java code, since
Hadoop has no framework in place yet for other types of unit tests.
* test-patch now exits with a failure status if problems arise trying to do git
checkouts. Previously the exit code was success.
> rewrite test-patch.sh
> ---------------------
>
> Key: HADOOP-11746
> URL: https://issues.apache.org/jira/browse/HADOOP-11746
> Project: Hadoop Common
> Issue Type: Test
> Components: build, test
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Fix For: 2.8.0
>
> Attachments: HADOOP-11746-00.patch, HADOOP-11746-01.patch,
> HADOOP-11746-02.patch, HADOOP-11746-03.patch, HADOOP-11746-04.patch,
> HADOOP-11746-05.patch, HADOOP-11746-06.patch, HADOOP-11746-07.patch,
> HADOOP-11746-09.patch, HADOOP-11746-10.patch, HADOOP-11746-11.patch,
> HADOOP-11746-12.patch, HADOOP-11746-13.patch, HADOOP-11746-14.patch,
> HADOOP-11746-15.patch, HADOOP-11746-16.patch, HADOOP-11746-17.patch,
> HADOOP-11746-18.patch, HADOOP-11746-19.patch, HADOOP-11746-20.patch,
> HADOOP-11746-21.branch-2.patch, HADOOP-11746-21.patch
>
>
> This code is bad and you should feel bad.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
