See <https://builds.apache.org/job/log4net-trunk-tests/61/display/redirect>
------------------------------------------ Started by upstream project "log4net-trunk-build" build number 186 originally caused by: Started by an SCM change Started by an SCM change Started by upstream project "log4net-trunk-build" build number 187 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on windows-2012-2 (Windows) in workspace <https://builds.apache.org/job/log4net-trunk-tests/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/logging-log4net.git # timeout=10 Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/logging-log4net.git > git --version # timeout=10 > git fetch --tags --progress > https://git-wip-us.apache.org/repos/asf/logging-log4net.git > +refs/heads/*:refs/remotes/origin/* Seen branch in repository origin/abandoned/log4net-1.3.x Seen branch in repository origin/develop Seen branch in repository origin/feature/RollingFileAppender-NG Seen branch in repository origin/feature/build-multibranch Seen branch in repository origin/master Seen branch in repository origin/pr/old/10 Seen branch in repository origin/pr/old/22 Seen branch in repository origin/pr/old/28 Seen branch in repository origin/pr/old/29 Seen branch in repository origin/pr/old/32 Seen branch in repository origin/pr/old/40 Seen branch in repository origin/pr/old/43 Seen branch in repository origin/pr/old/45 Seen branch in repository origin/pr/old/7 Seen branch in repository origin/pr/old/9 Seen 15 remote branches > git tag -l # timeout=10 > git rev-parse "refs/tags/rc/1.2.14-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.14-RC2^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/2.0.8-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/1.2.13^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/2.0.6-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/1.2.12^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/1.2.15^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/1.2.14^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/1.2.9^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.13-RC3^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/2.0.7-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.13-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.13-RC2^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/2.0.8^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.15-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/1.2.13RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/1.2.11^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.12-RC1^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/1.2.10^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/2.0.7^{commit}" # timeout=10 > git rev-parse "refs/tags/rel/2.0.6^{commit}" # timeout=10 > git rev-parse "refs/tags/rc/1.2.10-RC2^{commit}" # timeout=10 Multiple candidate revisions Scheduling another build to catch up with log4net-trunk-tests Checking out Revision 66bdcb14261a76d5bf4ba84c670f73306ba4326c (origin/abandoned/log4net-1.3.x) > git config core.sparsecheckout # timeout=10 > git checkout -f 66bdcb14261a76d5bf4ba84c670f73306ba4326c First time build. Skipping changelog. Executing command: cmd.exe /C "F:\jenkins\tools\nant\nant-0.92\bin\NAnt.exe -buildfile:log4net.build compile-net-4.0 && exit %%ERRORLEVEL%%" [log4net-trunk-tests] $ cmd.exe /C "F:\jenkins\tools\nant\nant-0.92\bin\NAnt.exe -buildfile:log4net.build compile-net-4.0 && exit %%ERRORLEVEL%%" NAnt 0.92 (Build 0.92.4543.0; release; 6/9/2012) Copyright (C) 2001-2012 Gerry Shaw http://nant.sourceforge.net BUILD FAILED <https://builds.apache.org/job/log4net-trunk-tests/ws/log4net.build>: Error loading buildfile. Could not find file '<https://builds.apache.org/job/log4net-trunk-tests/ws/log4net.build'.> For more information regarding the cause of the build failure, run the build again in debug mode. Try 'nant -help' for more information Build step 'Execute NAnt build' marked build as failure
