Comment 1 for bug 1001265

Revision history for this message
Andy Doan (doanac) wrote :

This is the wget/tar issue we've had. Here's the relevant part of the failure:

root@master:~# [rc=0]: wget --no-proxy --connect-timeout=30 -S -O- http://192.1 68.1.10/images/tmp/tmp992bse/system.tar.bz2 --progress=dot -e dotbytes=2M | tar --numeric-owner -C /mnt/lava -xjf -
--2012-05-18 05:18:07-- http://192.168.1.10/images/tmp/tmp992bse/system.tar.bz2
Connecting to 192.168.1.10:80... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 200 OK
  Date: Fri, 18 May 2012 05:19:40 GMT
  Server: Apache/2.2.20 (Ubuntu)
  Last-Modified: Fri, 18 May 2012 05:17:12 GMT
  ETag: "da077c-938abb1-4c048aa38fabf"
  Accept-Ranges: bytes
  Content-Length: 154708913
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: application/x-bzip2
Length: 154708913 (148M) [application/x-bzip2]
Saving to: `STDOUT'

     0K .......... .......... .......... .<LAVA_DISPATCHER>2012-05-18 05:29:40 AM ERROR: Android deployment failed
<LAVA_DISPATCHER>2012-05-18 05:29:40 AM INFO: Android image deployment exiting
<LAVA_DISPATCHER>2012-05-18 05:29:40 AM WARNING: [ACTION-E] deploy_linaro_android_image is finished with error (Android deployment failed).
<LAVA_DISPATCHER>2012-05-18 05:29:41 AM INFO: Dashboard : http://validation.linaro.org/lava-server/dashboard/permalink/bundle/2558afa6fc814b7fc213db31a6ce2bc4fadb2c1e/