[
https://issues.apache.org/jira/browse/HADOOP-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563319#comment-14563319
]
Sidharta Seethana commented on HADOOP-12002:
--------------------------------------------
The mistake I made was to set {{FINDBUGS_HOME}} to
{{/usr/local/Cellar/findbugs/3.0.0}} instead of
{{/usr/local/Cellar/findbugs/3.0.0/libexec}} as specified below. So this issue
is indeed not as common as I thought it would be. That said, adding a +1 due to
an invalid {{FINDBUGS_HOME}} could cause unnecessary patch iterations on the
corresponding JIRA (as it did in my case).
{code}
brew info findbugs
findbugs: stable 3.0.0
http://findbugs.sourceforge.net/index.html
Conflicts with: fb-client
/usr/local/Cellar/findbugs/3.0.0 (156 files, 11M) *
Built from source
From:
https://github.com/Homebrew/homebrew/blob/master/Library/Formula/findbugs.rb
==> Caveats
Some tools might refer findbugs by env variable.
After installation, set $FINDBUGS_HOME in your profile:
export FINDBUGS_HOME=/usr/local/Cellar/findbugs/3.0.0/libexec
{brew info findbugs
findbugs: stable 3.0.0
http://findbugs.sourceforge.net/index.html
Conflicts with: fb-client
/usr/local/Cellar/findbugs/3.0.0 (156 files, 11M) *
Built from source
From:
https://github.com/Homebrew/homebrew/blob/master/Library/Formula/findbugs.rb
==> Caveats
Some tools might refer findbugs by env variable.
After installation, set $FINDBUGS_HOME in your profile:
export FINDBUGS_HOME=/usr/local/Cellar/findbugs/3.0.0/libexec
{code}
> test-patch.sh needs to verify all of the findbugs tools exist
> -------------------------------------------------------------
>
> Key: HADOOP-12002
> URL: https://issues.apache.org/jira/browse/HADOOP-12002
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Sidharta Seethana
> Assignee: Kengo Seki
> Priority: Critical
> Labels: test-patch
> Attachments: HADOOP-12002.001.patch, HADOOP-12002.002.patch
>
>
> {{test-patch.sh}} was used with {{FINDBUGS_HOME}} set. See below for an
> example - there were 4 findbugs warnings generated - however,
> {{test-patch.sh}} doesn't seem to realize that there are missing findbugs
> tools and +1s the finbugs check.
> {quote}
> Running findbugs in
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
> mvn clean test findbugs:findbugs -DskipTests -DhadoopPatchProcess >
> /private/tmp/hadoop-test-patch/71089/patchFindBugsOutputhadoop-yarn-server-nodemanager.txt
> 2>&1
> <snip>hadoop/dev-support/test-patch.sh: line 1907:
> /usr/local/Cellar/findbugs/3.0.0/bin/setBugDatabaseInfo: No such file or
> directory
> <snip>hadoop/dev-support/test-patch.sh: line 1915:
> /usr/local/Cellar/findbugs/3.0.0/bin/filterBugs: No such file or directory
> Found Findbugs warnings
> (<snip>hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/findbugsXml.xml)
> <snip>hadoop/dev-support/test-patch.sh: line 1921:
> /usr/local/Cellar/findbugs/3.0.0/bin/convertXmlToText: No such file or
> directory
> [Mon May 18 18:08:52 PDT 2015 DEBUG]: Stop clock
> Elapsed time: 0m 38s
> {quote}
> Findbugs check reported as successful :
> {quote}
> | +1 | findbugs | 0m 38s | The patch does not introduce any
> | | | | new Findbugs (version 3.0.0)
> | | | | warnings.
> | | | 23m 51s |
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
