Actually --fail-at-end did not work. Though build moved on to next module, it did not deploy the one with the failed tests. I had to do add -Dmaven.test.failure.ignore=true to get https://builds.apache.org/job/Tez-Build/478/ passing and publish the artifacts. Reverted -Dmaven.test.failure.ignore=true as it is not good to have it, but kept --fail-at-end so that build shows tests failures in all modules instead of terminating at the first failure. Also added -DdeployAtEnd=true (Build 479) now itself so that we don't have inconsistent snapshots. So till the test failures are fixed, if snapshots need to be published, -Dmaven.test.failure.ignore=true needs to be added to the build.
-Rohini On Fri, Jul 4, 2014 at 10:53 PM, Hitesh Shah <hit...@apache.org> wrote: > Hi Rohini > > For now, I think fixing the build to use fail-at-end would be the best > option. I don’t have build configure permissions so if you could make the > change that would be great. Also, would you mind filing a jira that we > should revert the build to deploy-at-end later once the tests are fixed? > > I think the tests do require a bit more investigation given that different > tests fail randomly. I saw Rajesh’s patch but I am not sure whether a > timeout increase will fix the issue permanently. > > thanks > — Hitesh > > > On Jul 4, 2014, at 10:31 PM, Rohini Palaniswamy <rohini.adi...@gmail.com> > wrote: > > > Hitesh, > > I see that you have filed Blocker jiras for the 3 failing tests and > Rajesh has put a patch for one increasing timeout from 10 to 45 seconds. Is > the fix going to be increasing timeout or going to investigate the cause as > the low timeouts in test seem to be for a reason. Can I still go ahead with > --fail-at-end for one build and revert it back after without waiting for > the fixes for those? I have worked around by building and installing in > local maven, but would like to have this fixed sooner so that I can wrap up > and post some of my pig tez patches. > > > > -Rohini > > > > > > On Fri, Jul 4, 2014 at 10:09 PM, Rohini Palaniswamy < > rohini.adi...@gmail.com> wrote: > > Actually it is not going through. Looks like Hitesh also kicked it off > couple of times. They pass fine in the laptop but Jenkins is always hitting > one test failure (not the same one always). The failing tests in > TestContainerReuse have 10 or 15 second timeout and it might take time to > debug if that is due to a recently introduced change or because the build > host is slow. It would be good to fix the build script to use --fail-at-end > till then so that it does publish all snapshots without causing > inconsistency even if there are test failures or do > http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd > so that it does not publish snapshots at all if there is a test failure. > > > > I seem to have permissions to modify the build. Can I modify it to > include --fail-at-end and kick off a build to fix the inconsistencies? > > > > Regards, > > Rohini > > > > > > On Fri, Jul 4, 2014 at 8:43 PM, Bikas Saha <bi...@hortonworks.com> > wrote: > > Thanks Rohini for the back up J > > > > > > > > *From:* Rohini Palaniswamy [mailto:rohini.adi...@gmail.com] > > *Sent:* Friday, July 04, 2014 1:28 PM > > *To:* dev@tez.incubator.apache.org > > *Cc:* u...@tez.incubator.apache.org > > *Subject:* Re: Breaking change in TezClient > > > > > > > > Bikas, > > > > https://builds.apache.org/job/Tez-Build/467/console failed due to a > > transient test failure and so > > > http://repository.apache.org/content/groups/snapshots/org/apache/tez/tez-dag/0.5.0-incubating-SNAPSHOT/ > > still had older snapshot while tez-api, etc had ones after your commit. > > This caused failures with CNFE for TezSession in tez-dag code while > > compiling and running in pig against latest tez snapshot from maven. I > have > > kicked of the build again. > > > > > > > > Regards, > > > > Rohini > > > > > > > > > > > > On Thu, Jul 3, 2014 at 6:19 PM, Bikas Saha <bi...@hortonworks.com> > wrote: > > > > https://issues.apache.org/jira/browse/TEZ-692 > > > > > > > > The final comments at the end should have all you need to build again. > > Should be straight-forward and localized. > > > > > > > > Let me know if there are any issues. > > > > Bikas > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > > > > > >
