The branch change should happen after Yetus has already read the personality from master.
IIRC, our personality passes "-DHBasePatchProcess" to get test profiles activated. If that doesn't activate that Jenkins related profile maybe we should just change to activating it expressly via "-pjenkins.patch". We could then ensure that profile is present in all branches. -- Sean Busbey On Feb 18, 2016 10:59, "Stack" <st...@duboce.net> wrote: > On Thu, Feb 18, 2016 at 8:54 AM, Nick Dimiduk <ndimi...@apache.org> wrote: > > > Hi folks, > > > > Looking for confirmation over in the precommit runs on HBASE-15169, it > > looks to me like the rerunning of flakies is no longer happening. Used to > > be we had junit running a test 3 or 4 times before it was determined to > be > > a failure. Any pointers on how to get that back? > > > > > Seems to happen on master[1] but I don't see it on your branch-1.1 run in > HBASE-15169. > > Command for your HBASE-15169 branch-1.1 run was: > > mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hbase-branch-1.1-1 > -DHBasePatchProcess clean test -fae > > ... and for the below master run with retry of flakies: > > mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hbase-master-0 > -DHBasePatchProcess -PrunAllTests clean test -fae > > Our pom has a profile, jenkins.patch, that will do rerunFailingTestsCount > with value of 2. I don't see it getting explicitly invoked. > > I think main difference is that master has a hbase-personality.sh in > dev-support whereas hbase-1.1 does not have it. I see up in the jenkins > build, if present, we'll pass it as args to yetus. Want to try a backport? > > St.Ack > > 1. > > https://builds.apache.org/job/PreCommit-HBASE-Build/588/artifact/patchprocess/patch-unit-hbase-server-jdk1.7.0_95.txt > > > > Thanks, > > Nick > > >
