The errors from earlier builds (and the last failing on for Solr-reference-guide-master) seem to indicate a possible Ruby version issue, if this SO article is a valid clue: https://stackoverflow.com/questions/40085215/listen-conflict-when-installing-jekyll-with-docker
"listen" is installed with the jekyll gem as a dependency. See also https://github.com/guard/listen and notes about Ruby versions there. Not clear to me why this would have suddenly changed - I checked release history for these gems and Jekyll did have a new version release Jun 15, but I think we would have seen this way earlier if it was from dependency changes in that update. Let me know if you need help looking into this further. On Wed, Jul 12, 2017 at 7:22 PM, Steve Rowe <sar...@gmail.com> wrote: > I’ve disabled the ref guide builds until I can get to the bottom of the Ruby > problems. > > -- > Steve > www.lucidworks.com > >> On Jul 12, 2017, at 8:18 PM, Apache Jenkins Server >> <jenk...@builds.apache.org> wrote: >> >> Build: https://builds.apache.org/job/Solr-reference-guide-7.0/66/ >> >> Log: >> Started by user sarowe >> [EnvInject] - Loading node environment variables. >> Building remotely on H20 (git-websites) in workspace >> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-7.0 >>> 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/branch_7_0^{commit} # timeout=10 >>> git rev-parse refs/remotes/origin/origin/branch_7_0^{commit} # timeout=10 >> Checking out Revision 8c000d9ae67ce3a6942173263570b3b1770bd788 >> (refs/remotes/origin/branch_7_0) >>> git config core.sparsecheckout # timeout=10 >>> git checkout -f 8c000d9ae67ce3a6942173263570b3b1770bd788 >>> git rev-list 8c000d9ae67ce3a6942173263570b3b1770bd788 # timeout=10 >> No emails were triggered. >> [Solr-reference-guide-7.0] $ /bin/bash -xe /tmp/hudson1083622664334795049.sh >> + echo 'Set ruby path to avoid writing to /usr directory' >> Set ruby path to avoid writing to /usr directory >> + export RUBY_PATH=/home/jenkins/shared/.rvm >> + RUBY_PATH=/home/jenkins/shared/.rvm >> + export GEM_HOME=/home/jenkins/shared/.rvm/gems >> + GEM_HOME=/home/jenkins/shared/.rvm/gems >> + curl -sSL https://get.rvm.io >> + grep -v __rvm_print_headline >> + bash -s stable --ruby --path /home/jenkins/shared/.rvm >> Downloading https://github.com/rvm/rvm/archive/1.29.2.tar.gz >> Downloading >> https://github.com/rvm/rvm/releases/download/1.29.2/1.29.2.tar.gz.asc >> Found PGP signature at: >> 'https://github.com/rvm/rvm/releases/download/1.29.2/1.29.2.tar.gz.asc', >> but no GPG software exists to validate it, skipping. >> >> Upgrading the RVM installation in /home/jenkins/shared/.rvm/ >> RVM PATH line found in /home/jenkins/.mkshrc /home/jenkins/.profile >> /home/jenkins/.bashrc /home/jenkins/.zshrc. >> RVM sourcing line found in /home/jenkins/.profile >> /home/jenkins/.bash_profile /home/jenkins/.zlogin. >> Upgrade of RVM in /home/jenkins/shared/.rvm/ is complete. >> >> # jenkins, >> # >> # Thank you for using RVM! >> # We sincerely hope that RVM helps to make your life easier and more >> enjoyable!!! >> # >> # ~Wayne, Michal & team. >> >> In case of problems: https://rvm.io/help and https://twitter.com/rvm_io >> >> Upgrade Notes: >> >> * It looks like some old stuff is laying around RVM, you can cleanup with: >> rvm cleanup all >> >> * No new notes to display. >> >> Warning! PATH is not properly set up, '/home/jenkins/shared/.rvm/gems/bin' >> is not available. >> Usually this is caused by shell initialization files. Search for >> 'PATH=...' entries. >> You can also re-add RVM to your profile by running: 'rvm get stable >> --auto-dotfiles'. >> To fix it temporarily in this shell session run: 'rvm use gems'. >> To ignore this error add rvm_silence_path_mismatch_check_flag=1 to >> your ~/.rvmrc file. >> Searching for binary rubies, this might take some time. >> Found remote file >> https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/16.04/x86_64/ruby-2.4.0.tar.bz2 >> Checking requirements for ubuntu. >> Installing requirements for ubuntu. >> Updating system... >> Error running 'requirements_debian_update_system ruby-2.4.0', >> showing last 15 lines of >> /home/jenkins/shared/.rvm/log/1499905133_ruby-2.4.0/update_system.log >> ++ /scripts/functions/utility : __rvm_try_sudo() 377 > [[ -d /usr/sbin ]] >> ++ /scripts/functions/utility : __rvm_try_sudo() 377 > [[ >> :/home/jenkins/tools/java/latest1.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/jenkins/shared/.rvm/bin: >> != *\:\/\u\s\r\/\s\b\i\n\:* ]] >> ++ /scripts/functions/utility : __rvm_try_sudo() 375 > for sbin_path in >> /sbin /usr/sbin /usr/local/sbin >> ++ /scripts/functions/utility : __rvm_try_sudo() 377 > [[ -d >> /usr/local/sbin ]] >> ++ /scripts/functions/utility : __rvm_try_sudo() 377 > [[ >> :/home/jenkins/tools/java/latest1.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/jenkins/shared/.rvm/bin: >> != *\:\/\u\s\r\/\l\o\c\a\l\/\s\b\i\n\:* ]] >> ++ /scripts/functions/utility : __rvm_try_sudo() 381 > [[ -n '' ]] >> ++ /scripts/functions/utility : __rvm_try_sudo() 384 > >> command_to_run=(__rvm_sudo -p "%p password required for '$*': " >> "${command_to_run[@]}") >> ++ /scripts/functions/utility : __rvm_try_sudo() 391 > __rvm_sudo -p '%p >> password required for '\''apt-get --quiet --yes update'\'': ' apt-get >> --quiet --yes update >> ++ /scripts/functions/support : __rvm_sudo() 358 > command sudo -p '%p >> password required for '\''apt-get --quiet --yes update'\'': ' apt-get >> --quiet --yes update >> ++ /scripts/functions/support : __rvm_sudo() 358 > sudo -p '%p password >> required for '\''apt-get --quiet --yes update'\'': ' apt-get --quiet --yes >> update >> sudo: PAM authentication error: User not known to the underlying >> authentication module >> ++ /scripts/functions/utility : __rvm_try_sudo() 391 > return 1 >> ++ /scripts/functions/requirements/ubuntu : >> requirements_debian_update_system() 43 > typeset __ret=1 >> ++ /scripts/functions/requirements/ubuntu : >> requirements_debian_update_system() 44 > case ${__ret} in >> ++ /scripts/functions/requirements/ubuntu : >> requirements_debian_update_system() 53 > return 1 >> Requirements installation failed with status: 1. >> 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: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
