Failed to setup container for test |
|||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win10, MacOS 10.12, etc...) What steps will reproduce the problem? (1)schedule a test (2) (3) What is the expected result? The test sets up a container What happens instead? Failed to setup container for test: Container test_205334992_1528081111_4317 already exists.. Check logs in ssp_logs folder for more details. This happens on some tests not all of them. Here are 3 examples of tests failing with this issue. https://stainless.corp.google.com/search?view=list&first_date=2018-06-02&last_date=2018-06-04&test=%5Efirmware_Cr50DeepSleepStress%24%7C%5Efirmware_Cr50DeepSleepStress%5C.reboot%24%7C%5Efirmware_Cr50UpdateScriptStress%24&build=R6%5B5-9%5D&board=%5Escarlet%24&status=FAIL&status=ERROR&status=ABORT&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true
,
Jun 4 2018
https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1086224
,
Jun 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/4eb0d53ee7ea904088067e8cbde54f68d267ba52 commit 4eb0d53ee7ea904088067e8cbde54f68d267ba52 Author: Prathmesh Prabhu <pprabhu@chromium.org> Date: Fri Jun 08 06:33:26 2018 [autotest] lxc: Cleanup patially successful container clone When retrying container clone() call without snapshot, it is necessary to cleanup any artifacts from a partially successful clone() before. BUG= chromium:849412 TEST=None Change-Id: I58de535b1df61e3297d4d398275a1084dd286e08 Reviewed-on: https://chromium-review.googlesource.com/1086224 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Jacob Kopczynski <jkop@chromium.org> [modify] https://crrev.com/4eb0d53ee7ea904088067e8cbde54f68d267ba52/site_utils/lxc/container_factory.py
,
Jun 8 2018
,
Jun 12 2018
We are still seeing this on scarlet in the cr50 stress pool. Do you know why? https://stainless.corp.google.com/search?view=list&first_date=2018-06-11&last_date=2018-06-12&suite=%5Ecr50%5C_stress%5C_experimental%24&build=R6%5B5-9%5D&board=scarlet&status=FAIL&status=ERROR&status=ABORT&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false
,
Jun 12 2018
Pending prod push. We're trying a push today. Hit some problems with that. |
|||
►
Sign in to add a comment |
|||
Comment 1 by mruthven@chromium.org
, Jun 4 2018