Hi Nick
> Does Jenkins ensure only one HBasePatchProcess runs on a given host at a
time?
Yes, there is no concurrent build on the same machine. You're always alone.
It's unlikely to change: it's already difficult enough to parallelize
things for a single product; doing it between multiple products
On Thu, Dec 13, 2012 at 2:40 PM, Stack wrote:
>
> Want to try removing it for a while?
I attached a couple simple patches to
https://issues.apache.org/jira/browse/HBASE-7350. Maybe someone who knows
more about the different layers of test harness and Jenkins build slave
configuration can commen
On Thu, Dec 13, 2012 at 2:33 PM, Nick Dimiduk wrote:
> I don't think so. The last act of test-patch.sh is to print the banner
> "Finished build." and exit. What does Jenkins do after it runs this script?
> Regardless, I no longer believe this is causing the endemic build failures.
> I'm more susp
On Thu, Dec 13, 2012 at 1:19 PM, Stack wrote:
> > What does the -DHBasePatchProcess flag do? A `git grep` yields no
> results.
>
> I don't know.
>
> I see it made up in ./dev-support/test-patch.sh
>
> 3 $MVN clean test -DskipTests -D${PROJECT_NAME}PatchProcess >
> $PATCH_DIR/trunkJavacWarnings
On Thu, Dec 13, 2012 at 11:56 AM, Nick Dimiduk wrote:
> @Stack: Hey now, let's not get to hasty!
>
>
Just sent you all my life savings, $50.00, and signed over to you my first
and second born.
> @Nicolas,
>
> Looking at the output of #3526 [0], where does this bash
> script /tmp/hudson4033738
@Stack: Hey now, let's not get to hasty!
@Nicolas,
Looking at the output of #3526 [0], where does this bash
script /tmp/hudson4033738860406301156.sh come from?
What does the -DHBasePatchProcess flag do? A `git grep` yields no results.
The step "Determining number of patched javadoc warnings." w
On Thu, Dec 13, 2012 at 10:24 AM, Nick Dimiduk wrote:
> Hi guys,
>
> Every build in recent history run by the PreCommit job [0] has failed. For
> some of them, this is the usual suspect of a patch not applying cleanly.
> But for many, the issue looks like a simple configuration issue. Case in
> p
For #3526, I think it's marked wrong because one test timeouted. This is
not really well managed in surefire today.
I actually hope that the next version (2.13) will improve this.
I think that we also have builds marked as bad with this:
{color:red}-1 javadoc{color}. The javadoc tool appears
Looks like there might be a hanging test:
Tests run: 1238, Failures: 0, Errors: 0, Skipped: 11
Cheers
On Thu, Dec 13, 2012 at 10:24 AM, Nick Dimiduk wrote:
> Hi guys,
>
> Every build in recent history run by the PreCommit job [0] has failed. For
> some of them, this is the usual suspect of a p
Hi guys,
Every build in recent history run by the PreCommit job [0] has failed. For
some of them, this is the usual suspect of a patch not applying cleanly.
But for many, the issue looks like a simple configuration issue. Case in
point, this one [1] looks like Jenkins simply failed to read a value
10 matches
Mail list logo
