EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Build failed in Jenkins: epics-pvaPy-linux32 #784
From: APS Jenkins via Core-talk <[email protected]>
To: [email protected]
Date: Mon, 12 Aug 2019 05:21:54 -0500 (CDT)
See <https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/784/display/redirect>

------------------------------------------
Started by upstream project "epics-pvaClient-linux32" build number 609
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on linux32-uranus (linux32) in workspace <https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/>
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/epics-base/pvaPy.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 https://github.com/epics-base/pvaPy.git
 > git --version # timeout=10
Setting http proxy: webproxy1.anl.gov:9091
 > git fetch --tags --progress https://github.com/epics-base/pvaPy.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 8a37c43f62308fba7edc7e6227243f5f6cf42bca (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 8a37c43f62308fba7edc7e6227243f5f6cf42bca
Commit message: "add multichannel tests"
 > git rev-list --no-walk 8a37c43f62308fba7edc7e6227243f5f6cf42bca # timeout=10
[epics-pvaPy-linux32] $ /bin/sh -xe /tmp/jenkins5907482181285243045.sh
+ rm -rf epics
+ mkdir -p epics
+ ln -s /local/jenkins/workspace/epics-base-3.16-linux32 epics/base
+ ln -s /local/jenkins/workspace/epics-pvCommon-linux32 epics/pvCommonCPP
+ ln -s /local/jenkins/workspace/epics-pvData-linux32 epics/pvDataCPP
+ ln -s /local/jenkins/workspace/epics-normativeTypes-linux32 epics/normativeTypesCPP
+ ln -s /local/jenkins/workspace/epics-pvAccess-linux32 epics/pvAccessCPP
+ ln -s /local/jenkins/workspace/epics-pvaClient-linux32 epics/pvaClientCPP
+ ln -s /local/jenkins/workspace/epics-pvDatabase-linux32 epics/pvDatabaseCPP
+ EPICS_BASE=<https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/epics/base>
+ EPICS4_DIR=<https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/epics>
+ make configure
autoreconf --install tools/autoconf
configure.ac:2: installing `./install-sh'
configure.ac:2: installing `./missing'
tools/autoconf/configure --with-top=.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... none
checking for python... /usr/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for a version of Python >= 2.7... no
configure: error: this package requires Python >= 2.7.
If you have it installed, but it isn't the default Python
interpreter in your system path, please pass the PYTHON_VERSION
variable to configure. See ``configure --help'' for reference.

Makefile:53: recipe for target 'configure' failed
make: *** [configure] Error 1
Build step 'Execute shell' marked build as failure

Replies:
Jenkins build is back to normal : epics-pvaPy-linux32 #785 APS Jenkins via Core-talk
References:
Build failed in Jenkins: epics-pvaPy-linux32 #783 APS Jenkins via Core-talk

Navigate by Date:
Prev: Build failed in Jenkins: epics-pvaPy-linux32 #783 APS Jenkins via Core-talk
Next: Jenkins build is back to normal : epics-pvaPy-linux32 #785 APS Jenkins via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Build failed in Jenkins: epics-pvaPy-linux32 #783 APS Jenkins via Core-talk
Next: Jenkins build is back to normal : epics-pvaPy-linux32 #785 APS Jenkins via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
ANJ, 12 Aug 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·