← Back to team overview

maas-builds team mailing list archive

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

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

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

[...truncated 4558 lines...]
2014-02-03 01:21:05 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:08 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:11 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:14 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:17 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:20 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:23 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:26 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:29 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:32 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:35 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:38 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:41 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:44 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:47 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:50 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:53 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:56 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:21:59 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:02 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:05 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:08 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:11 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:14 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:17 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:20 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:23 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:26 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:29 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:32 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:35 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:38 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:41 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:44 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:47 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:50 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:53 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:56 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:22:59 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:02 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:05 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:08 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:11 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:14 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:17 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:20 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:23 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:26 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:29 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:32 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:35 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:38 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:41 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:44 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:47 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:50 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:53 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:56 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:23:59 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:02 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:05 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:08 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:11 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:14 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:17 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:20 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:23 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:26 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:29 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:32 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:35 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:38 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:41 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:44 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:47 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:50 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:53 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:56 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:24:59 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:02 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:05 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:08 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:11 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:14 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:17 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:20 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:23 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:26 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:29 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:32 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:35 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:38 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:41 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:44 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:47 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:50 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:53 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:56 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:25:59 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:26:02 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:26:05 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:26:08 DEBUG juju.state open.go:88 connection failed, will retry: dial tcp 192.168.21.10:37017: no route to host
2014-02-03 01:26:09 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.cVvPZn/ubtree0-build/real-tree/debian/tests/utils.py", line 69, in wrapper
    result = func(*args, **kwargs)
  File "/tmp/adt-run.cVvPZn/ubtree0-build/real-tree/debian/tests/maas-integration.py", line 618, in test_juju_bootstrap
    self._wait_machines_running(1)
  File "/tmp/adt-run.cVvPZn/ubtree0-build/real-tree/debian/tests/maas-integration.py", line 623, in _wait_machines_running
    status = self.get_juju_status()
  File "/tmp/adt-run.cVvPZn/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.cVvPZn/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.cVvPZn/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.cVvPZn/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.0004s
maas-integration.TestMAASIntegration.test_check_dhcp_service: 0.0266s
maas-integration.TestMAASIntegration.test_check_initial_services: 0.0342s
maas-integration.TestMAASIntegration.test_update_preseed_arm: 0.0591s
maas-integration.TestMAASIntegration.test_restart_provisioning_server: 0.0597s
maas-integration.TestMAASIntegration.test_restart_dbus_avahi: 0.1303s
maas-integration.TestMAASIntegration.test_create_admin: 0.1504s
maas-integration.TestMAASIntegration.test_cluster_connected: 0.1993s
maas-integration.TestMAASIntegration.test_apply_tag_to_all_nodes: 0.2136s
maas-integration.TestMAASIntegration.test_commission_nodes: 0.4471s
maas-integration.TestMAASIntegration.test_boot_nodes_enlist: 0.4731s
maas-integration.TestMAASIntegration.test_update_dns_config: 1.3259s
maas-integration.TestMAASIntegration.test_update_maas_url: 2.1965s
maas-integration.TestMAASIntegration.test_set_nodes_ipmi_config: 2.4666s
maas-integration.TestMAASIntegration.test_login_api: 2.8511s
maas-integration.TestMAASIntegration.test_set_up_dhcp_region: 4.4823s
maas-integration.TestMAASIntegration.test_check_tag_applied_to_all_nodes: 5.4348s
maas-integration.TestMAASIntegration.test_configure_juju: 5.8251s
maas-integration.TestMAASIntegration.test_check_nodes_declared: 161.5779s
maas-integration.TestMAASIntegration.test_check_nodes_ready: 193.4477s
maas-integration.TestMAASIntegration.test_import_pxe_files: 482.2366s
maas-integration.TestMAASIntegration.test_juju_bootstrap: 3000.0344s
----------------------------------------------------------------------
Ran 24 tests in 3863.860s

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.cVvPZn:-/|/tmp/adt-run.cVvPZn/!
+ 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-02 20:34:16: Failure: adt-run exited with status 4.\n
2014-02-02 20:34:16: 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-02 20:34:19: Info: Test artifacts copied to /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results\n
2014-02-02 20:34:19: 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-03_00-25-32 ]
+ 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-02 20:34:19: Failure: Test didn't end normally. Generating error file\n
2014-02-02 20:34:19: 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_20140202-203419.error
+ echo saucy amd64 maas
+ rsync -a /home/ubuntu/jenkins-jobs/workspace/saucy-adt-maas-daily/results/saucy_amd64_maas_20140202-203419.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-02 20:34:20: Info: Cleaning up\n
2014-02-02 20:34:20: Info: Cleaning up
+ [ -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140202_192556.HlhFcX.img.pid ]
+ cat /var/tmp/adt/disks/run/saucy-amd64-maas-20140202_192556.HlhFcX.img.pid
+ kill -9 8477
+ rm -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140202_192556.HlhFcX.img.pid
+ rm -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140202_192556.HlhFcX.img
+ rm -f /var/tmp/adt/disks/run/saucy-amd64-maas-20140202_192556.HlhFcX.img.monitor /var/tmp/adt/disks/run/saucy-amd64-maas-20140202_192556.HlhFcX.img.serial
+ rm -f /var/lock/adt/ssh.54323.lock
+ rm -f /var/lock/adt/vnc.5911.lock
+ [ -d /tmp/adt-amd64.3ixXk4 ]
+ rm -Rf /tmp/adt-amd64.3ixXk4
+ 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