← Back to team overview

maas-builds team mailing list archive

  1. maas-builds team
  2. Mailing list archive
  3. Message #00225

Jenkins Still Failing - saucy-adt-maas-daily 56

  Thread Previous • Date Previous • • Thread Next 
See http://d-jenkins.ubuntu-ci:8080/job/saucy-adt-maas-daily/56/

[...truncated 4537 lines...]
2014-02-02 01:22:48 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:22:51 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:22:54 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:22:57 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:00 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:03 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:06 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:09 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:12 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:15 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:18 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:21 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:24 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:27 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:30 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:33 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:36 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:39 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:42 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:45 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:48 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:51 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:54 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:23:57 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:00 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:03 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:06 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:09 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:12 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:15 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:18 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:21 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:24 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:27 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:30 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:33 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:36 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:39 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:42 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:45 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:48 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:51 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:54 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:24:57 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:00 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:03 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:06 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:09 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:12 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:15 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:18 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:21 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:24 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:27 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:30 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:33 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:36 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:39 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:42 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:45 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:48 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:51 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:54 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:25:57 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:00 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:03 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:06 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:09 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:12 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:15 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:18 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:21 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:24 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:27 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:30 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:33 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:36 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:39 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:42 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:45 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:48 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:51 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:54 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:26:57 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:00 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:03 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:06 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:09 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:12 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:15 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:18 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:21 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:24 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:27 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:30 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:33 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:36 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:39 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:42 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:45 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:48 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:51 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.13:37017: no route to host
2014-02-02 01:27:51 ERROR juju supercommand.go:282 Unable to connect to environment "".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
no reachable servers
}}}

Traceback (most recent call last):
  File "/tmp/adt-run.sHWS1r/ubtree0-build/real-tree/debian/tests/utils.py", line 69, in wrapper
    result = func(*args, **kwargs)
  File "/tmp/adt-run.sHWS1r/ubtree0-build/real-tree/debian/tests/maas-integration.py", line 618, in test_juju_bootstrap
    self._wait_machines_running(1)
  File "/tmp/adt-run.sHWS1r/ubtree0-build/real-tree/debian/tests/maas-integration.py", line 623, in _wait_machines_running
    status = self.get_juju_status()
  File "/tmp/adt-run.sHWS1r/ubtree0-build/real-tree/debian/tests/maas-integration.py", line 603, in get_juju_status
    status_output = self._run_juju_command(["status"])
  File "/tmp/adt-run.sHWS1r/ubtree0-build/real-tree/debian/tests/maas-integration.py", line 587, in _run_juju_command
    retcode, output, err = run_command(command)
  File "/tmp/adt-run.sHWS1r/ubtree0-build/real-tree/debian/tests/utils.py", line 82, in run_command
    stdout, stderr = process.communicate()
  File "/usr/lib/python2.7/subprocess.py", line 798, in communicate
    return self._communicate(input)
  File "/usr/lib/python2.7/subprocess.py", line 1400, in _communicate
    stdout, stderr = self._communicate_with_poll(input)
  File "/usr/lib/python2.7/subprocess.py", line 1454, in _communicate_with_poll
    ready = poller.poll()
  File "/tmp/adt-run.sHWS1r/ubtree0-build/real-tree/debian/tests/utils.py", line 63, in _handle_timeout
    raise TimeoutError(error_message)
TimeoutError: Timer expired


maas-integration.TestMAASIntegration.test_update_pxe_config: 0.0006s
maas-integration.TestMAASIntegration.test_update_preseed_arm: 0.0339s
maas-integration.TestMAASIntegration.test_restart_provisioning_server: 0.0612s
maas-integration.TestMAASIntegration.test_check_initial_services: 0.0627s
maas-integration.TestMAASIntegration.test_restart_dbus_avahi: 0.1455s
maas-integration.TestMAASIntegration.test_create_admin: 0.1485s
maas-integration.TestMAASIntegration.test_cluster_connected: 0.2012s
maas-integration.TestMAASIntegration.test_apply_tag_to_all_nodes: 0.2060s
maas-integration.TestMAASIntegration.test_commission_nodes: 0.3857s
maas-integration.TestMAASIntegration.test_boot_nodes_enlist: 0.4398s
maas-integration.TestMAASIntegration.test_update_maas_url: 1.1899s
maas-integration.TestMAASIntegration.test_update_dns_config: 1.2857s
maas-integration.TestMAASIntegration.test_login_api: 1.4177s
maas-integration.TestMAASIntegration.test_set_nodes_ipmi_config: 2.4547s
maas-integration.TestMAASIntegration.test_set_up_dhcp_region: 2.5128s
maas-integration.TestMAASIntegration.test_check_dhcp_service: 5.1033s
maas-integration.TestMAASIntegration.test_check_tag_applied_to_all_nodes: 5.4391s
maas-integration.TestMAASIntegration.test_configure_juju: 6.3000s
maas-integration.TestMAASIntegration.test_check_nodes_declared: 161.5511s
maas-integration.TestMAASIntegration.test_check_nodes_ready: 193.5094s
maas-integration.TestMAASIntegration.test_import_pxe_files: 482.9301s
maas-integration.TestMAASIntegration.test_juju_bootstrap: 3000.0303s
----------------------------------------------------------------------
Ran 24 tests in 3865.600s

FAILED (SKIP=3, errors=1)
adt-run1: testbed executing test finished with exit status 1
adt-run: & ubtree0t-maas-package-test: ----------------------------------------]
adt-run: & ubtree0t-maas-package-test:  - - - - - - - - - - results - - - - - - - - - -
ubtree0t-maas-package-test FAIL non-zero exit status 1
adt-run1: ** needs_reset, previously=False
adt-run: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests done.
adt-run1: ** stop
adt-run1: ** close, scratch=tb-scratch~/tmp/adt-run.sHWS1r:-/|/tmp/adt-run.sHWS1r/!
+ RC=4
+ [ 4 -eq 20 ]
+ [ 0 -eq 1 ]
+ [ -x /home/ubuntu/adt-export-result ]
+ RES=PASS
+ [ 4 -gt 0 ]
+ RES=FAIL
+ /home/ubuntu/adt-export-result -D /root/adt-log maas FAIL
+ chown -R ubuntu /root/adt-log /var/tmp/testresults
+ chmod og+r /var/log/syslog
+ ls /var/crash/
+ [ -n  ]
+ exit 4
Connection to localhost closed.
+ RET=4
+ [ 0 -eq 1 ]
+ [ 4 -gt 0 ]
+ log_failure_msg adt-run exited with status 4.
+ log_msg Failure: adt-run exited with status 4.\n
+ date +%F %X
+ printf 2014-02-01 20:35:54: Failure: adt-run exited with status 4.\n
2014-02-01 20:35:54: Failure: adt-run exited with status 4.
+ [ 0 -eq 0 ]
+ mkdir -p /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/disks/adtkey -p 54323 -tt -o BatchMode=yes -l ubuntu localhost sudo chown -R ubuntu /root/adt-log; find /root/adt-log -type f -empty | xargs rm 2>/dev/null
Warning: Permanently added '[localhost]:54323' (ECDSA) to the list of known hosts.
find: `/root/adt-log': Permission denied
Connection to localhost closed.
+ true
+ scp -r -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/disks/adtkey -P 54323 ubuntu@localhost:/root/adt-log/* /var/crash/*crash /var/log/syslog /var/tmp/testresults /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results
+ true
+ log_info_msg Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results
+ log_msg Info: Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results\n
+ date +%F %X
+ printf 2014-02-01 20:35:57: Info: Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results\n
2014-02-01 20:35:57: Info: Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results
+ [ -f /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results/summary.log ]
+ [ -n 2014-02-02_00-26-35 ]
+ ls -tr /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results/*.result
+ tail -1
+ resfile=
+ [ -n  ]
+ log_failure_msg Test didn't end normally. Generating error file
+ log_msg Failure: Test didn't end normally. Generating error file\n
+ date +%F %X
+ printf 2014-02-01 20:35:57: Failure: Test didn't end normally. Generating error file\n
2014-02-01 20:35:57: Failure: Test didn't end normally. Generating error file
+ date +%Y%m%d-%H%M%S
+ errfile=/home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results/saucy_amd64_maas_20140201-203557.error
+ echo saucy amd64 maas
+ rsync -a /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results/saucy_amd64_maas_20140201-203557.error /saucy/tmp/
rsync: mkdir "/saucy/tmp" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.0]
+ true
+ [ 0 -eq 0 ]
+ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /var/tmp/adt/disks/adtkey -p 54323 -tt -o BatchMode=yes -l ubuntu localhost sudo poweroff
Warning: Permanently added '[localhost]:54323' (ECDSA) to the list of known hosts.
Connection to localhost closed.
+ exit 4
+ on_exit
+ log_info_msg Cleaning up
+ log_msg Info: Cleaning up\n
+ date +%F %X
+ printf 2014-02-01 20:35:57: Info: Cleaning up\n
2014-02-01 20:35:57: Info: Cleaning up
+ [ -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140201_192659.4LUbIM.img.pid ]
+ cat /var/tmp/adt/disks/run/saucy-amd64-maas-20140201_192659.4LUbIM.img.pid
+ kill -9 13593
+ rm -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140201_192659.4LUbIM.img.pid
+ rm -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140201_192659.4LUbIM.img
+ rm -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140201_192659.4LUbIM.img.monitor /var/tmp/adt/disks/run/saucy-amd64-maas-20140201_192659.4LUbIM.img.serial
+ rm -f /var/lock/adt/ssh.54323.lock
+ rm -f /var/lock/adt/vnc.5911.lock
+ [ -d /tmp/adt-amd64.C60biY ]
+ rm -Rf /tmp/adt-amd64.C60biY
+ rm -f /var/tmp/adt/disks/run/saucy-amd64-maas-*.img*
+ find /var/lock/adt -name *.lock -mtime +1
+ exit 4
Build step 'Execute shell' marked build as failure
Archiving artifacts
Email was triggered for: Failure
Sending email for trigger: Failure

Follow ups

References

  Thread Previous • Date Previous • • Thread Next