Aha, thanks for figuring the Jenkins thing out Uwe. -- Steve www.lucidworks.com
> On Feb 17, 2016, at 1:25 PM, Uwe Schindler <[email protected]> wrote: > > Hehe, > > for this checkout the "Clean Before Checkout" option was missing in Jenkins > (5.x). Steve cloned this for 5.5, too. This is why every 2nd build fails. > > I am clicking through Jenkins and checking all jobs. It is a pity that we > don't have the "mass change" plugin on ASF Jenkins to change the same option > for many Jobs. > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: [email protected] > > >> -----Original Message----- >> From: Uwe Schindler [mailto:[email protected]] >> Sent: Wednesday, February 17, 2016 7:21 PM >> To: [email protected] >> Subject: RE: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure >> >> But why does this fail on Jenkins? Jenkins starts with cleaned checkout.... >> >> I will check the Jenkins Config of this Job, maybe it is missing the extra >> GIT >> checkout option ("git reset"). >> >> Uwe >> >> ----- >> Uwe Schindler >> H.-H.-Meier-Allee 63, D-28213 Bremen >> http://www.thetaphi.de >> eMail: [email protected] >> >>> -----Original Message----- >>> From: Dawid Weiss [mailto:[email protected]] >>> Sent: Wednesday, February 17, 2016 4:44 PM >>> To: [email protected] >>> Subject: Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure >>> >>> This is actually very predictable -- if you run it once, it succeeds. >>> If you re-run it then (without cleaning) it always fails, even with >>> -v. I filed this and mention the problem's cause, but I won't have the >>> time to fix it -- sorry! >>> >>> https://issues.apache.org/jira/browse/LUCENE-7033 >>> >>> Dawid >>> >>> On Tue, Feb 16, 2016 at 3:50 PM, Michael McCandless >>> <[email protected]> wrote: >>>> OK I ran without -v, piping to a file, and it succeeds. >>>> >>>> Then I run straight to the console, without -v, and it fails. >>>> >>>> I'll see if I can get it to fail with -v... >>>> >>>> Mike McCandless >>>> >>>> http://blog.mikemccandless.com >>>> >>>> On Tue, Feb 16, 2016 at 5:26 AM, Dawid Weiss <[email protected]> >>> wrote: >>>>> Can you: >>>>> >>>>> ant -v > output.log 2>&1 >>>>> >>>>> Perhaps it's a timing issue when -v is dumped to the console? >>>>> >>>>> Dawid >>>>> >>>>> >>>>> On Tue, Feb 16, 2016 at 10:59 AM, Michael McCandless >>>>> <[email protected]> wrote: >>>>>> I could still use some help on this one! >>>>>> >>>>>> Somehow this succeeds when I run "ant -v" fails otherwise. >>>>>> >>>>>> Mike McCandless >>>>>> >>>>>> http://blog.mikemccandless.com >>>>>> >>>>>> >>>>>> On Tue, Feb 16, 2016 at 1:32 AM, Apache Jenkins Server >>>>>> <[email protected]> wrote: >>>>>>> Build: https://builds.apache.org/job/Lucene-Artifacts-5.x/1088/ >>>>>>> >>>>>>> No tests ran. >>>>>>> >>>>>>> Build Log: >>>>>>> [...truncated 8805 lines...] >>>>>>> BUILD FAILED >>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts- >>> 5.x/lucene/build.xml:427: The following error occurred while executing this >>> line: >>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts- >>> 5.x/lucene/build.xml:415: The following error occurred while executing this >>> line: >>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts- >>> 5.x/lucene/common-build.xml:1724: The following error occurred while >>> executing this line: >>>>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts- >>> 5.x/lucene/common-build.xml:608: Error installing artifact >>> 'org.apache.lucene:lucene-core:jar': Error installing artifact: File >>> /x1/jenkins/jenkins-slave/workspace/Lucene-Artifacts- >>> 5.x/lucene/build/lucene.tgz.unpacked/lucene-5.6.0-1088/core/lucene- >> core- >>> 5.6.0-1088.jar does not exist >>>>>>> >>>>>>> Total time: 4 minutes 52 seconds >>>>>>> Build step 'Invoke Ant' marked build as failure >>>>>>> Archiving artifacts >>>>>>> Compressed 167.65 MB of artifacts by 22.5% relative to #1087 >>>>>>> Publishing Javadoc >>>>>>> Email was triggered for: Failure - Any >>>>>>> Sending email for trigger: Failure - Any >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
