cloud_Toolbox failing on lakitu-paladin |
||||
Issue descriptionlakitu-paladin has had two consecutive failures and appears to be caused by content on a external debian server failing a checksum. https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-paladin/builds/3969 https://storage.cloud.google.com/chromeos-image-archive/lakitu-paladin/R54-8685.0.0-rc4/gce_test_results_2/test_harness/failed/SimpleTestVerify/2_autotest_tests/suite_gce-smoke/results-10-cloud_Toolbox/status?_ga=1.70554128.1874465609.1460005926 ERROR cloud_Toolbox cloud_Toolbox timestamp=1470671712 localtime=Aug 08 15:55:12 Command <toolbox apt-get update> failed, rc=100, Command returned non-zero exit status * Command: toolbox apt-get update Exit status: 100 Duration: 2.19270396233 stdout: Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB] Get:2 http://security.debian.org jessie/updates/main amd64 Packages [382 kB] Ign http://httpredir.debian.org jessie InRelease Get:3 http://httpredir.debian.org jessie-updates InRelease [142 kB] Get:4 http://httpredir.debian.org jessie Release.gpg [2373 B] Get:5 http://httpredir.debian.org jessie-backports InRelease [166 kB] Get:6 http://httpredir.debian.org jessie-updates/main amd64 Packages [17.6 kB] Get:7 http://httpredir.debian.org jessie Release [148 kB] Get:8 http://httpredir.debian.org jessie/main amd64 Packages [9032 kB] Get:9 http://httpredir.debian.org jessie-backports/main amd64 Packages [834 kB] Fetched 10.8 MB in 2s (5034 kB/s) stderr: Spawning container root-debian-jessie-backports on /var/lib/toolbox/root-debian-jessie-backports. Press ^] three times within 1s to kill container. W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. Container root-debian-jessie-backports failed with error code 100. END ERROR cloud_Toolbox cloud_Toolbox timestamp=1470671712 localtime=Aug 08 15:55:12
,
Aug 8 2016
,
Aug 8 2016
lakitu-incremental failed in the same way with https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-incremental/builds/10561 but succeeded with https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-incremental/builds/10562 so hopefully this was just a transient issue which has now corrected itself.
,
Aug 8 2016
yeah, this might be a transient issue. digging up online suggests that this might happen because package mirrors have not fully caught up with updates. I also see that the timestamps on packages is of today "08-Aug-2016" ( http://mirrors.kernel.org/debian/dists/jessie-backports/main/binary-amd64/). So it very well might be the case that we hit them while they were being updated. Anyways, lets monitor for some more time and see if it gets resolved. cc'd our oncall as well.
,
Aug 9 2016
After a few intermittent failures, the builders are green again. Closing this bug.
,
Aug 9 2016
If this happens again, I think we should look at changing the test to not have external dependencies. Intermittent failures across a few tests add up given the number of tests and builds that we run, and it ends up being particular problematic if the flakes start failing CQ runs.
,
Aug 9 2016
For this particular case, we are working on optimizing the feature being tested itself. It will allow us to get rid of this external dependency from the test too.
,
Aug 13 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/autotest-lakitu/+/f21ee949418be612977d408c3270466f4d33e4ea commit f21ee949418be612977d408c3270466f4d33e4ea Author: Aditya Kali <adityakali@google.com> Date: Fri Aug 12 01:39:37 2016 |
||||
►
Sign in to add a comment |
||||
Comment 1 by davidri...@chromium.org
, Aug 8 2016