EPICS Home

Experimental Physics and Industrial Control System


 
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
<== Date ==> <== Thread ==>
Subject: Build failed in Jenkins: epics-example-win64 #749
From: APS Jenkins via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Tue, 29 Mar 2022 05:37:59 -0500 (CDT) 
See <https://jenkins.aps.anl.gov/job/epics-example-win64/749/display/redirect>

Changes:


------------------------------------------
Started by upstream project "epics-pvaClient-win64" build number 644
originally caused by:
 Started by upstream project "epics-normativeTypes-win64" build number 543
 originally caused by:
  Started by upstream project "epics-pvData-win64" build number 583
  originally caused by:
   Started by upstream project "epics-base-7.0-win64" build number 297
   originally caused by:
    Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on win64-2 (windows-x64) in workspace <https://jenkins.aps.anl.gov/job/epics-example-win64/ws/>
The recommended git tool is: NONE
No credentials specified
 > C:/Program Files/Git/cmd/git.exe rev-parse --resolve-git-dir C:\jenkins\win64-2\workspace\epics-example-win64\.git # timeout=10
Fetching changes from the remote Git repository
 > C:/Program Files/Git/cmd/git.exe config remote.origin.url https://github.com/epics-base/exampleCPP.git # timeout=10
Cleaning workspace
 > C:/Program Files/Git/cmd/git.exe rev-parse --verify HEAD # timeout=10
Resetting working tree
 > C:/Program Files/Git/cmd/git.exe reset --hard # timeout=10
 > C:/Program Files/Git/cmd/git.exe clean -fdx # timeout=10
Fetching upstream changes from https://github.com/epics-base/exampleCPP.git
 > C:/Program Files/Git/cmd/git.exe --version # timeout=10
 > git --version # 'git version 2.20.1.windows.1'
Setting http proxy: webproxy1.anl.gov:9091
 > C:/Program Files/Git/cmd/git.exe fetch --tags --force --progress -- https://github.com/epics-base/exampleCPP.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > C:/Program Files/Git/cmd/git.exe rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
Checking out Revision bf816da88471171afc6c6b5ed6f912289336c30e (refs/remotes/origin/master)
 > C:/Program Files/Git/cmd/git.exe config core.sparsecheckout # timeout=10
 > C:/Program Files/Git/cmd/git.exe checkout -f bf816da88471171afc6c6b5ed6f912289336c30e # timeout=10
Commit message: "add putAlarm and putTimeStamp"
 > C:/Program Files/Git/cmd/git.exe rev-list --no-walk bf816da88471171afc6c6b5ed6f912289336c30e # timeout=10
[epics-example-win64] $ cmd /c call C:\Users\jenkins\AppData\Local\Temp\jenkins7011140086735153877.bat

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>SET TA=win64 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>SET BV=7.0 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>SET CR=configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>SET MO=-j4 -O --no-print-directory 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>SET WS=C:/Jenkins/win64-2/workspace 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo # RELEASE for jenkins-epics-example-win64-749 1>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo PVDATABASE = C:/Jenkins/win64-2/workspace/epics-pvDatabase-win64 1>>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo PVACLIENT = C:/Jenkins/win64-2/workspace/epics-pvaClient-win64 1>>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo PVA2PVA = C:/Jenkins/win64-2/workspace/epics-pva2pva-win64 1>>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo PVACCESS = C:/Jenkins/win64-2/workspace/epics-pvAccess-win64 1>>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo NORMATIVE = C:/Jenkins/win64-2/workspace/epics-normativeTypes-win64 1>>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo PVDATA = C:/Jenkins/win64-2/workspace/epics-pvData-win64 1>>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>echo EPICS_BASE = C:/Jenkins/win64-2/workspace/epics-base-7.0-win64 1>>configure/RELEASE.local 

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>make -j4 -O --no-print-directory 
'make' is not recognized as an internal or external command,
operable program or batch file.

jenkins@JEEVES C:\jenkins\win64-2\workspace\epics-example-win64>exit 9009 
Build step 'Execute Windows batch command' marked build as failure
[MSBuild] Skipping execution of recorder since overall result is 'FAILURE'
Replies:
Jenkins build is back to normal : epics-example-win64 #750 APS Jenkins via Core-talk
Navigate by Date:
Prev: epics-base-7.0-win64s-test - Build # 379 - Unstable! APS Jenkins via Core-talk
Next: Build failed in Jenkins: epics-pvaClient-win64s #606 APS Jenkins via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
Navigate by Thread:
Prev: epics-base-7.0-win64s-test - Build # 380 - Fixed! APS Jenkins via Core-talk
Next: Jenkins build is back to normal : epics-example-win64 #750 APS Jenkins via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024