[
https://issues.apache.org/jira/browse/HBASE-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-3225.
--------------------------
Resolution: Fixed
Fix Version/s: 0.90.0
Assignee: Gary Helmling
My fault.
There is a config history up on hudson. Looking at it, I see the following:
2010-11-05_23-22-48 Changed stack View as XML (RAW)
2010-10-11_14-58-25
In the above, I changed the goals from ...
clean -Dmaven.test.redirectTestOutputToFile=true deploy
to
clean -Dmaven.test.redirectTestOutputToFile=true install assembly:assembly
The latter runs the tests twice -- once on install and again doing
assembly:assembly
I changed it to do instead
lean -Dmaven.test.redirectTestOutputToFile=true site assembly:assembly
Well spotted Gary.
> Hudson running "test" target twice for trunk builds
> ---------------------------------------------------
>
> Key: HBASE-3225
> URL: https://issues.apache.org/jira/browse/HBASE-3225
> Project: HBase
> Issue Type: Task
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Fix For: 0.90.0
>
>
> This seems to be a recent occurrence (or at least I noticed it recently).
> For builds of trunk, Hudson is invoking the "test" target twice in a row,
> see: https://hudson.apache.org/hudson/job/HBase-TRUNK/1643/console
> Looks like it's running once for "install" and once for "assembly:assembly".
> On our internal Hudson setup, we saw the same issue and fixed by changing the
> project targets from "clean install assembly:assembly" to just "clean
> assembly:assembly". Would be good for someone with more mvn knowledge to
> confirm this is the right fix though. And if so we should make the same
> change in the ASF Hudson config. No reason for Hudson builds to be slower
> than they need to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
