Build failed in Jenkins: saucy-upgrade-raring-server » amd64,non-lts,server,upgrade-test #56

[Jenkins Notification]

See <http://10.189.74.2:8080/job/saucy-upgrade-raring-server/./ARCH=amd64,LTS=non-lts,PROFILE=server,label=upgrade-test/56/>

------------------------------------------
Started by upstream project "saucy-upgrade-raring-server" build number 56
[EnvInject] - Loading node environment variables.
Building remotely on wazn-upgrade
[upgrade-test] $ /bin/sh -x /tmp/hudson4931391539338900228.sh
+ rm -Rf results
+ BRANCH=auto-upgrade-testing
+ distro-info -d
+ RELEASE=saucy
+ [ -d auto-upgrade-testing ]
+ bzr branch lp:auto-upgrade-testing
bzr: ERROR: Connection error: while sending POST /bazaar/: [Errno 110] Connection timed out
+ cd auto-upgrade-testing
/tmp/hudson4931391539338900228.sh: 13: cd: can't cd to auto-upgrade-testing
+ LTSPREFIX=
+ ARCHEXT=
+ BASEDIR=/home/upgrade-tester/auto-upgrade-tester
+ [ non-lts = non-lts ]
+ LTSPREFIX=
+ ARCHEXT=amd64
+ PROFILENAME=saucy-server-amd64
+ echo Running profile saucy-server-amd64
Running profile saucy-server-amd64
+ PYTHONCMD=
+ python -c import DistUpgrade
+ bin/auto-upgrade-tester /home/upgrade-tester/auto-upgrade-tester/profiles/saucy-server-amd64
/tmp/hudson4931391539338900228.sh: 41: /tmp/hudson4931391539338900228.sh: bin/auto-upgrade-tester: not found
+ cp -ar /home/upgrade-tester/auto-upgrade-tester/result/saucy-server-amd64/ <http://10.189.74.2:8080/job/saucy-upgrade-raring-server/./ARCH=amd64,LTS=non-lts,PROFILE=server,label=upgrade-test/ws/results>
Archiving artifacts
Recording test results
Test reports were found but none of them are new. Did tests run? 
For example, <http://10.189.74.2:8080/job/saucy-upgrade-raring-server/./ARCH=amd64,LTS=non-lts,PROFILE=server,label=upgrade-test/56/artifact/results/results.xml> is 1 day 23 hr old

Build step 'Publish JUnit test result report' changed build result to FAILURE