You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2016/02/16 07:32:45 UTC
[JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
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
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Dawid Weiss <da...@gmail.com>.
> No nitpicking, please. I just wrote that it resets checkout to pristine
> state.
I wasn't trying? git reset won't delete any ignored files (like the
build/ folder) -- so either we differ in what a "pristine" state is or
you have a wrong understanding of git reset.
Try it on your local checkout after you've built Lucene or something:
git reset
The build folder will still be there.
D.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Chris Hostetter <ho...@fucit.org>.
: >Everything else... well, I don't understand why it does so much, let's
: >leave it at that :)
:
: I think it does that to get the changes since last build. No idea what
: rev-parseand rev-list do, this is the git hell and there is no escape.
it's general jenkins plumbing that can serve various configuration
options / trigger conditions ...
the rev-parse lines are to figure out what commit SHA to associate with
this build (in a way that also works with paramaterized build that takes
in tag names or shorthand partial SHAs), so it can know if the current
commit on the specified branch is diff from the last build (some people
have time based triggers that only build if there is new revisions on the
branch). It checks this twice with two diff branches (just in case you
forgot to start your branch spec with "origin".
the rev-list lines are for getting the list of changes for this build
(allthough it admitedly seems really scary that cmmand doesn't
specify two SHAs and/or include a --max-count param ... i guess jenkins
assumes you'll never have billions of commits in your git rep)
:
: Uwe
:
: >D.
: >
: >
: >On Wed, Feb 17, 2016 at 10:05 PM, Uwe Schindler <uw...@thetaphi.de>
: >wrote:
: >> That's what it does with that option on ASF:
: >>
: >> Started by upstream project "Lucene-Solr-NightlyTests-5.x" build
: >number 1100
: >> originally caused by:
: >> Started by timer
: >> [EnvInject] - Loading node environment variables.
: >> Building remotely on lucene in workspace
: >> /home/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x
: >>> git rev-parse --is-inside-work-tree # timeout=10
: >> Fetching changes from the remote Git repository
: >>> git config remote.origin.url git://git.apache.org/lucene-solr.git #
: >>> timeout=10
: >> Cleaning workspace
: >>> git rev-parse --verify HEAD # timeout=10
: >> Resetting working tree
: >>> git reset --hard # timeout=10
: >>> git clean -fdx # timeout=10
: >> Fetching upstream changes from git://git.apache.org/lucene-solr.git
: >>> git --version # timeout=10
: >>> git -c core.askpass=true fetch --tags --progress
: >>> git://git.apache.org/lucene-solr.git
: >+refs/heads/*:refs/remotes/origin/*
: >>> git rev-parse refs/remotes/origin/branch_5x^{commit} # timeout=10
: >>> git rev-parse refs/remotes/origin/origin/branch_5x^{commit} #
: >timeout=10
: >> Checking out Revision 56d426f814c090443b20e90f81969f5c060ca490
: >> (refs/remotes/origin/branch_5x)
: >>> git config core.sparsecheckout # timeout=10
: >>> git checkout -f 56d426f814c090443b20e90f81969f5c060ca490
: >>> git rev-list 56d426f814c090443b20e90f81969f5c060ca490 # timeout=10
: >> No emails were triggered.
: >> [lucene] $
: >>
: >/home/jenkins/jenkins-slave/tools/hudson.tasks.Ant_AntInstallation/ant-1.8.2/bin/ant
: >> -file build.xml -Dversion.suffix=1090 prepare-release-no-sign
: >>
: >> This is so horrible that I don't want to see it. :)
: >>
: >> I use my local git only with a GUI, that's fine to me.
: >>
: >> The issue here was just a misunderstanding, wrong terms used by
: >non-git
: >> fanatic people. To me a reset of working copy is what I want to have.
: >If
: >> that's a git clean with crazy parameters I don't care. It should just
: >reset
: >> to what I expect from the term 'reset'.
: >>
: >> Uwe
: >>
: >> Am 17. Februar 2016 21:56:23 MEZ, schrieb Dawid Weiss
: >> <da...@gmail.com>:
: >>>>
: >>>> This is how it looks like (attached screenshot). This option was
: >>>> missing.
: >>>> Now all is fine.
: >>>> No need to discuss about git commands!
: >>>
: >>>
: >>> Fine, Uwe -- I was just mislead by your comment concerning "git
: >>> reset", that's all. The Jenkins option has nothing to do with git
: >>> reset, it very likely wipes the entire build folder and either
: >clones
: >>> from the remote anew or (smarter) clones from another local clone of
: >>> that remote repository.
: >>>
: >>> I admit there's something I don't understand in your heated replies
: >--
: >>> you always want to understand every detail of Java code yet you're
: >so
: >>> openly against trying to understand anything git-related. Why? It's
: >>> interesting, why resist it with such ferocity?
: >>>
: >>> Dawid
: >>>
: >>> P.S. For example, there is a huge performance difference between
: >>> what
: >>> Jenkins (above) probably does and my two git commands that result in
: >>> exactly the same output, but I'll leave the explanation since you
: >>> probably won't be interested anyway :)
: >>>
: >>> ________________________________
: >>>
: >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
: >>> For additional commands, e-mail: dev-help@lucene.apache.org
: >>>
: >>
: >> --
: >> Uwe Schindler
: >> H.-H.-Meier-Allee 63, 28213 Bremen
: >> http://www.thetaphi.de
: >
: >---------------------------------------------------------------------
: >To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
: >For additional commands, e-mail: dev-help@lucene.apache.org
:
: --
: Uwe Schindler
: H.-H.-Meier-Allee 63, 28213 Bremen
: http://www.thetaphi.de
:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
: For additional commands, e-mail: dev-help@lucene.apache.org
:
:
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Uwe Schindler <uw...@thetaphi.de>.
Am 17. Februar 2016 22:08:58 MEZ, schrieb Dawid Weiss <da...@gmail.com>:
>Ah... so the clean option is actually smarter than I thought -- it
>does exactly what I said!
>
>Resetting working tree
>> git reset --hard # timeout=10
>> git clean -fdx # timeout=10
As you see first line contains 'reset', and this is why I wrote 'git reset' in my mail. When checking the earlier build logs I was missing this line. And then repaired config!
>Everything else... well, I don't understand why it does so much, let's
>leave it at that :)
I think it does that to get the changes since last build. No idea what rev-parseand rev-list do, this is the git hell and there is no escape. :')
Uwe
>D.
>
>
>On Wed, Feb 17, 2016 at 10:05 PM, Uwe Schindler <uw...@thetaphi.de>
>wrote:
>> That's what it does with that option on ASF:
>>
>> Started by upstream project "Lucene-Solr-NightlyTests-5.x" build
>number 1100
>> originally caused by:
>> Started by timer
>> [EnvInject] - Loading node environment variables.
>> Building remotely on lucene in workspace
>> /home/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x
>>> git rev-parse --is-inside-work-tree # timeout=10
>> Fetching changes from the remote Git repository
>>> git config remote.origin.url git://git.apache.org/lucene-solr.git #
>>> timeout=10
>> Cleaning workspace
>>> git rev-parse --verify HEAD # timeout=10
>> Resetting working tree
>>> git reset --hard # timeout=10
>>> git clean -fdx # timeout=10
>> Fetching upstream changes from git://git.apache.org/lucene-solr.git
>>> git --version # timeout=10
>>> git -c core.askpass=true fetch --tags --progress
>>> git://git.apache.org/lucene-solr.git
>+refs/heads/*:refs/remotes/origin/*
>>> git rev-parse refs/remotes/origin/branch_5x^{commit} # timeout=10
>>> git rev-parse refs/remotes/origin/origin/branch_5x^{commit} #
>timeout=10
>> Checking out Revision 56d426f814c090443b20e90f81969f5c060ca490
>> (refs/remotes/origin/branch_5x)
>>> git config core.sparsecheckout # timeout=10
>>> git checkout -f 56d426f814c090443b20e90f81969f5c060ca490
>>> git rev-list 56d426f814c090443b20e90f81969f5c060ca490 # timeout=10
>> No emails were triggered.
>> [lucene] $
>>
>/home/jenkins/jenkins-slave/tools/hudson.tasks.Ant_AntInstallation/ant-1.8.2/bin/ant
>> -file build.xml -Dversion.suffix=1090 prepare-release-no-sign
>>
>> This is so horrible that I don't want to see it. :)
>>
>> I use my local git only with a GUI, that's fine to me.
>>
>> The issue here was just a misunderstanding, wrong terms used by
>non-git
>> fanatic people. To me a reset of working copy is what I want to have.
>If
>> that's a git clean with crazy parameters I don't care. It should just
>reset
>> to what I expect from the term 'reset'.
>>
>> Uwe
>>
>> Am 17. Februar 2016 21:56:23 MEZ, schrieb Dawid Weiss
>> <da...@gmail.com>:
>>>>
>>>> This is how it looks like (attached screenshot). This option was
>>>> missing.
>>>> Now all is fine.
>>>> No need to discuss about git commands!
>>>
>>>
>>> Fine, Uwe -- I was just mislead by your comment concerning "git
>>> reset", that's all. The Jenkins option has nothing to do with git
>>> reset, it very likely wipes the entire build folder and either
>clones
>>> from the remote anew or (smarter) clones from another local clone of
>>> that remote repository.
>>>
>>> I admit there's something I don't understand in your heated replies
>--
>>> you always want to understand every detail of Java code yet you're
>so
>>> openly against trying to understand anything git-related. Why? It's
>>> interesting, why resist it with such ferocity?
>>>
>>> Dawid
>>>
>>> P.S. For example, there is a huge performance difference between
>>> what
>>> Jenkins (above) probably does and my two git commands that result in
>>> exactly the same output, but I'll leave the explanation since you
>>> probably won't be interested anyway :)
>>>
>>> ________________________________
>>>
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>
>> --
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, 28213 Bremen
>> http://www.thetaphi.de
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>For additional commands, e-mail: dev-help@lucene.apache.org
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Dawid Weiss <da...@gmail.com>.
Ah... so the clean option is actually smarter than I thought -- it
does exactly what I said!
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Everything else... well, I don't understand why it does so much, let's
leave it at that :)
D.
On Wed, Feb 17, 2016 at 10:05 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
> That's what it does with that option on ASF:
>
> Started by upstream project "Lucene-Solr-NightlyTests-5.x" build number 1100
> originally caused by:
> Started by timer
> [EnvInject] - Loading node environment variables.
> Building remotely on lucene in workspace
> /home/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x
>> git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>> git config remote.origin.url git://git.apache.org/lucene-solr.git #
>> timeout=10
> Cleaning workspace
>> git rev-parse --verify HEAD # timeout=10
> Resetting working tree
>> git reset --hard # timeout=10
>> git clean -fdx # timeout=10
> Fetching upstream changes from git://git.apache.org/lucene-solr.git
>> git --version # timeout=10
>> git -c core.askpass=true fetch --tags --progress
>> git://git.apache.org/lucene-solr.git +refs/heads/*:refs/remotes/origin/*
>> git rev-parse refs/remotes/origin/branch_5x^{commit} # timeout=10
>> git rev-parse refs/remotes/origin/origin/branch_5x^{commit} # timeout=10
> Checking out Revision 56d426f814c090443b20e90f81969f5c060ca490
> (refs/remotes/origin/branch_5x)
>> git config core.sparsecheckout # timeout=10
>> git checkout -f 56d426f814c090443b20e90f81969f5c060ca490
>> git rev-list 56d426f814c090443b20e90f81969f5c060ca490 # timeout=10
> No emails were triggered.
> [lucene] $
> /home/jenkins/jenkins-slave/tools/hudson.tasks.Ant_AntInstallation/ant-1.8.2/bin/ant
> -file build.xml -Dversion.suffix=1090 prepare-release-no-sign
>
> This is so horrible that I don't want to see it. :)
>
> I use my local git only with a GUI, that's fine to me.
>
> The issue here was just a misunderstanding, wrong terms used by non-git
> fanatic people. To me a reset of working copy is what I want to have. If
> that's a git clean with crazy parameters I don't care. It should just reset
> to what I expect from the term 'reset'.
>
> Uwe
>
> Am 17. Februar 2016 21:56:23 MEZ, schrieb Dawid Weiss
> <da...@gmail.com>:
>>>
>>> This is how it looks like (attached screenshot). This option was
>>> missing.
>>> Now all is fine.
>>> No need to discuss about git commands!
>>
>>
>> Fine, Uwe -- I was just mislead by your comment concerning "git
>> reset", that's all. The Jenkins option has nothing to do with git
>> reset, it very likely wipes the entire build folder and either clones
>> from the remote anew or (smarter) clones from another local clone of
>> that remote repository.
>>
>> I admit there's something I don't understand in your heated replies --
>> you always want to understand every detail of Java code yet you're so
>> openly against trying to understand anything git-related. Why? It's
>> interesting, why resist it with such ferocity?
>>
>> Dawid
>>
>> P.S. For example, there is a huge performance difference between
>> what
>> Jenkins (above) probably does and my two git commands that result in
>> exactly the same output, but I'll leave the explanation since you
>> probably won't be interested anyway :)
>>
>> ________________________________
>>
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> --
> Uwe Schindler
> H.-H.-Meier-Allee 63, 28213 Bremen
> http://www.thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Uwe Schindler <uw...@thetaphi.de>.
That's what it does with that option on ASF:
Started by upstream project "Lucene-Solr-NightlyTests-5.x" build number 1100
originally caused by:
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on lucene in workspace /home/jenkins/jenkins-slave/workspace/Lucene-Artifacts-5.x
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/lucene-solr.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/lucene-solr.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress git://git.apache.org/lucene-solr.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/branch_5x^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/branch_5x^{commit} # timeout=10
Checking out Revision 56d426f814c090443b20e90f81969f5c060ca490 (refs/remotes/origin/branch_5x)
> git config core.sparsecheckout # timeout=10
> git checkout -f 56d426f814c090443b20e90f81969f5c060ca490
> git rev-list 56d426f814c090443b20e90f81969f5c060ca490 # timeout=10
No emails were triggered.
[lucene] $ /home/jenkins/jenkins-slave/tools/hudson.tasks.Ant_AntInstallation/ant-1.8.2/bin/ant -file build.xml -Dversion.suffix=1090 prepare-release-no-sign
This is so horrible that I don't want to see it. :)
I use my local git only with a GUI, that's fine to me.
The issue here was just a misunderstanding, wrong terms used by non-git fanatic people. To me a reset of working copy is what I want to have. If that's a git clean with crazy parameters I don't care. It should just reset to what I expect from the term 'reset'.
Uwe
Am 17. Februar 2016 21:56:23 MEZ, schrieb Dawid Weiss <da...@gmail.com>:
>> This is how it looks like (attached screenshot). This option was
>missing.
>> Now all is fine.
>> No need to discuss about git commands!
>
>Fine, Uwe -- I was just mislead by your comment concerning "git
>reset", that's all. The Jenkins option has nothing to do with git
>reset, it very likely wipes the entire build folder and either clones
>from the remote anew or (smarter) clones from another local clone of
>that remote repository.
>
>I admit there's something I don't understand in your heated replies --
>you always want to understand every detail of Java code yet you're so
>openly against trying to understand anything git-related. Why? It's
>interesting, why resist it with such ferocity?
>
>Dawid
>
>P.S. For example, there is a huge performance difference between what
>Jenkins (above) probably does and my two git commands that result in
>exactly the same output, but I'll leave the explanation since you
>probably won't be interested anyway :)
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>For additional commands, e-mail: dev-help@lucene.apache.org
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Dawid Weiss <da...@gmail.com>.
> This is how it looks like (attached screenshot). This option was missing.
> Now all is fine.
> No need to discuss about git commands!
Fine, Uwe -- I was just mislead by your comment concerning "git
reset", that's all. The Jenkins option has nothing to do with git
reset, it very likely wipes the entire build folder and either clones
from the remote anew or (smarter) clones from another local clone of
that remote repository.
I admit there's something I don't understand in your heated replies --
you always want to understand every detail of Java code yet you're so
openly against trying to understand anything git-related. Why? It's
interesting, why resist it with such ferocity?
Dawid
P.S. For example, there is a huge performance difference between what
Jenkins (above) probably does and my two git commands that result in
exactly the same output, but I'll leave the explanation since you
probably won't be interested anyway :)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
This is how it looks like (attached screenshot). This option was missing. Now all is fine.
No need to discuss about git commands!
Uwe
Am 17. Februar 2016 21:38:13 MEZ, schrieb Uwe Schindler <uw...@thetaphi.de>:
>No nitpicking, please. I just wrote that it resets checkout to pristine
>state. In fact the option in Jenkins does what it should. We don't need
>to discuss what it does behind scenes. I don't care about Gits horrible
>command line. :)
>
>In fact Policeman uses Eclipse JGit to do the same. You don't see any
>command line in log outputs - that's the best to me. ASF Jenkins prints
>tons of gitshit, just look into logs! :)
>
>Uwe
>
>Am 17. Februar 2016 20:59:25 MEZ, schrieb Dawid Weiss
><da...@gmail.com>:
>>> I will check the Jenkins Config of this Job, maybe it is missing the
>>extra GIT checkout option ("git reset").
>>
>>git reset actually only resets the tracked files that differ from the
>>head. What you're looking for is two things:
>>
>># resets any staged changes (not that there should be any on jenkins,
>>but for local repos there may be)
>>git reset --hard
>># clean ANY files not tracked in the repo -- this effectively restores
>>pristine state.
>>git clean -xfd .
>>
>>Dawid
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>For additional commands, e-mail: dev-help@lucene.apache.org
>
>--
>Uwe Schindler
>H.-H.-Meier-Allee 63, 28213 Bremen
>http://www.thetaphi.de
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Uwe Schindler <uw...@thetaphi.de>.
No nitpicking, please. I just wrote that it resets checkout to pristine state. In fact the option in Jenkins does what it should. We don't need to discuss what it does behind scenes. I don't care about Gits horrible command line. :)
In fact Policeman uses Eclipse JGit to do the same. You don't see any command line in log outputs - that's the best to me. ASF Jenkins prints tons of gitshit, just look into logs! :)
Uwe
Am 17. Februar 2016 20:59:25 MEZ, schrieb Dawid Weiss <da...@gmail.com>:
>> I will check the Jenkins Config of this Job, maybe it is missing the
>extra GIT checkout option ("git reset").
>
>git reset actually only resets the tracked files that differ from the
>head. What you're looking for is two things:
>
># resets any staged changes (not that there should be any on jenkins,
>but for local repos there may be)
>git reset --hard
># clean ANY files not tracked in the repo -- this effectively restores
>pristine state.
>git clean -xfd .
>
>Dawid
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>For additional commands, e-mail: dev-help@lucene.apache.org
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Dawid Weiss <da...@gmail.com>.
> I will check the Jenkins Config of this Job, maybe it is missing the extra GIT checkout option ("git reset").
git reset actually only resets the tracked files that differ from the
head. What you're looking for is two things:
# resets any staged changes (not that there should be any on jenkins,
but for local repos there may be)
git reset --hard
# clean ANY files not tracked in the repo -- this effectively restores
pristine state.
git clean -xfd .
Dawid
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Steve Rowe <sa...@gmail.com>.
Aha, thanks for figuring the Jenkins thing out Uwe.
--
Steve
www.lucidworks.com
> On Feb 17, 2016, at 1:25 PM, Uwe Schindler <uw...@thetaphi.de> 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: uwe@thetaphi.de
>
>
>> -----Original Message-----
>> From: Uwe Schindler [mailto:uwe@thetaphi.de]
>> Sent: Wednesday, February 17, 2016 7:21 PM
>> To: dev@lucene.apache.org
>> 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: uwe@thetaphi.de
>>
>>> -----Original Message-----
>>> From: Dawid Weiss [mailto:dawid.weiss@gmail.com]
>>> Sent: Wednesday, February 17, 2016 4:44 PM
>>> To: dev@lucene.apache.org
>>> 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
>>> <lu...@mikemccandless.com> 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 <da...@gmail.com>
>>> 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
>>>>> <lu...@mikemccandless.com> 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
>>>>>> <je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Michael McCandless <lu...@mikemccandless.com>.
Whoa, thank you Dawid and Uwe for digging into this!!
Mike McCandless
http://blog.mikemccandless.com
On Wed, Feb 17, 2016 at 1:25 PM, Uwe Schindler <uw...@thetaphi.de> 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: uwe@thetaphi.de
>
>
>> -----Original Message-----
>> From: Uwe Schindler [mailto:uwe@thetaphi.de]
>> Sent: Wednesday, February 17, 2016 7:21 PM
>> To: dev@lucene.apache.org
>> 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: uwe@thetaphi.de
>>
>> > -----Original Message-----
>> > From: Dawid Weiss [mailto:dawid.weiss@gmail.com]
>> > Sent: Wednesday, February 17, 2016 4:44 PM
>> > To: dev@lucene.apache.org
>> > 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
>> > <lu...@mikemccandless.com> 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 <da...@gmail.com>
>> > 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
>> > >> <lu...@mikemccandless.com> 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
>> > >>> <je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
>> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>>
>> > >>> ---------------------------------------------------------------------
>> > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > >>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>>
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > >> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > For additional commands, e-mail: dev-help@lucene.apache.org
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Uwe Schindler <uw...@thetaphi.de>.
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: uwe@thetaphi.de
> -----Original Message-----
> From: Uwe Schindler [mailto:uwe@thetaphi.de]
> Sent: Wednesday, February 17, 2016 7:21 PM
> To: dev@lucene.apache.org
> 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: uwe@thetaphi.de
>
> > -----Original Message-----
> > From: Dawid Weiss [mailto:dawid.weiss@gmail.com]
> > Sent: Wednesday, February 17, 2016 4:44 PM
> > To: dev@lucene.apache.org
> > 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
> > <lu...@mikemccandless.com> 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 <da...@gmail.com>
> > 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
> > >> <lu...@mikemccandless.com> 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
> > >>> <je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Uwe Schindler <uw...@thetaphi.de>.
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: uwe@thetaphi.de
> -----Original Message-----
> From: Dawid Weiss [mailto:dawid.weiss@gmail.com]
> Sent: Wednesday, February 17, 2016 4:44 PM
> To: dev@lucene.apache.org
> 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
> <lu...@mikemccandless.com> 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 <da...@gmail.com>
> 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
> >> <lu...@mikemccandless.com> 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
> >>> <je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Dawid Weiss <da...@gmail.com>.
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
<lu...@mikemccandless.com> 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 <da...@gmail.com> 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
>> <lu...@mikemccandless.com> 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
>>> <je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Michael McCandless <lu...@mikemccandless.com>.
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 <da...@gmail.com> 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
> <lu...@mikemccandless.com> 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
>> <je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Dawid Weiss <da...@gmail.com>.
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
<lu...@mikemccandless.com> 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
> <je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Artifacts-5.x - Build # 1088 - Failure
Posted by Michael McCandless <lu...@mikemccandless.com>.
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
<je...@builds.apache.org> 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: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org