I'm pretty sure none of the commits I did this afternoon caused this,
but possibly the changes for LUCENE-6144 did?

Also, I noticed the branch_7x Ref Guide build hasn't run in 1.5 days,
which is unrelated to this, I think, but warrants investigation.

On Thu, Nov 2, 2017 at 6:04 PM, Apache Jenkins Server
<[email protected]> wrote:
> Build: https://builds.apache.org/job/Solr-reference-guide-master/2994/
>
> Log:
> Started by timer
> [EnvInject] - Loading node environment variables.
> Building remotely on H19 (git-websites) in workspace 
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master
>  > 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 fetch --tags --progress git://git.apache.org/lucene-solr.git 
> +refs/heads/*:refs/remotes/origin/*
>  > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>  > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> Checking out Revision 19db1df81a18e6eb2cce5be973bf2305d606a9f8 
> (refs/remotes/origin/master)
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 19db1df81a18e6eb2cce5be973bf2305d606a9f8
> Commit message: "LUCENE-6144: Upgrade Ivy to 2.4.0; 'ant ivy-bootstrap' now 
> removes old Ivy jars in ~/.ant/lib/."
>  > git rev-list 42cc1c07f70af071b2ec7643b7e6c2d7e82cac81 # timeout=10
> No emails were triggered.
> [Solr-reference-guide-master] $ /usr/bin/env bash 
> /tmp/jenkins6785087023254441381.sh
> + set -e
> + RVM_PATH=/home/jenkins/.rvm
> + RUBY_VERSION=ruby-2.3.3
> + GEMSET=solr-refguide-gemset
> + curl -sSL https://get.rvm.io
> + bash -s -- --ignore-dotfiles stable
> Turning on ignore dotfiles mode.
> Downloading https://github.com/rvm/rvm/archive/1.29.3.tar.gz
> Downloading 
> https://github.com/rvm/rvm/releases/download/1.29.3/1.29.3.tar.gz.asc
> gpg: Signature made Sun 10 Sep 2017 08:59:21 PM UTC using RSA key ID BF04FF17
> gpg: Good signature from "Michal Papis (RVM signing) <[email protected]>"
> gpg:                 aka "Michal Papis <[email protected]>"
> gpg:                 aka "[jpeg image of size 5015]"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 409B 6B17 96C2 7546 2A17  0311 3804 BB82 D39D C0E3
>      Subkey fingerprint: 62C9 E5F4 DA30 0D94 AC36  166B E206 C29F BF04 FF17
> GPG verified '/home/jenkins/.rvm/archives/rvm-1.29.3.tgz'
>
> Upgrading the RVM installation in /home/jenkins/.rvm/
> Upgrade of RVM in /home/jenkins/.rvm/ is complete.
>
> Upgrade Notes:
>
>   * No new notes to display.
>
> + set +x
> Running 'source /home/jenkins/.rvm/scripts/rvm'
> Running 'rvm autolibs disable'
> Running 'rvm install ruby-2.3.3'
> Already installed ruby-2.3.3.
> To reinstall use:
>
>     rvm reinstall ruby-2.3.3
>
> Running 'rvm gemset create solr-refguide-gemset'
> ruby-2.3.3 - #gemset created 
> /home/jenkins/.rvm/gems/ruby-2.3.3@solr-refguide-gemset
> ruby-2.3.3 - #generating solr-refguide-gemset wrappers........
> Running 'rvm ruby-2.3.3@solr-refguide-gemset'
> Using /home/jenkins/.rvm/gems/ruby-2.3.3 with gemset solr-refguide-gemset
> Running 'gem install --force --version 3.5.0 jekyll'
> Successfully installed jekyll-3.5.0
> Parsing documentation for jekyll-3.5.0
> Done installing documentation for jekyll after 2 seconds
> 1 gem installed
> Running 'gem install --force --version 2.1.0 jekyll-asciidoc'
> Successfully installed jekyll-asciidoc-2.1.0
> Parsing documentation for jekyll-asciidoc-2.1.0
> Done installing documentation for jekyll-asciidoc after 0 seconds
> 1 gem installed
> Running 'gem install --force --version 1.1.2 pygments.rb'
> Successfully installed pygments.rb-1.1.2
> Parsing documentation for pygments.rb-1.1.2
> Done installing documentation for pygments.rb after 0 seconds
> 1 gem installed
> + ant clean build-site build-pdf
> Buildfile: 
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master/solr/solr-ref-guide/build.xml
>
> clean:
>
> build-init:
>     [mkdir] Created dir: 
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master/solr/build/solr-ref-guide/content
>      [echo] Copying all examples to build directory...
>      [copy] Copying 1 file to 
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master/solr/build/solr-ref-guide/content
>      [echo] Copying all non template files from src ...
>      [copy] Copying 377 files to 
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master/solr/build/solr-ref-guide/content
>      [echo] Copy (w/prop replacement) any template files from src...
>      [copy] Copying 1 file to 
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master/solr/build/solr-ref-guide/content
>
> ivy-availability-check:
>
> -ivy-fail-disallowed-ivy-version:
>      [echo] Please delete the following disallowed Ivy jar(s): 
> /home/jenkins/.ant/lib/ivy-2.3.0.jar
>
> BUILD FAILED
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master/lucene/common-build.xml:435:
>  The following error occurred while executing this line:
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master/lucene/common-build.xml:446:
>  Found disallowed Ivy jar(s): /home/jenkins/.ant/lib/ivy-2.3.0.jar
>
> Total time: 0 seconds
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> 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]

Reply via email to