New issue
Advanced search Search tips

Issue 696037 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Feb 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

platform_ImageLoaderServer test is very flaky

Project Member Reported by kerrnel@chromium.org, Feb 24 2017

Issue description

The platform_ImageLoaderServer test has become very flaky. Upon investigation, this appears to be caused by the test using the same component name ('PepperFlashPlayer') as real component updates, causing failures anytime a real component update is installed.
 
Labels: -Pri-3 OS-Chrome Pri-1
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/60f1671508825c26e77bdacf2687d805da00fc0e

commit 60f1671508825c26e77bdacf2687d805da00fc0e
Author: Greg Kerr <kerrnel@chromium.org>
Date: Fri Feb 24 22:24:46 2017

Fix component name collision.

The test is failing randomly and often because the test component name
(PepperFlashPlayer) collides with real component updates. Let us give it
a totally separate name to avoid such problem.

BUG= chromium:696037 
TEST=test_that -b ${BOARD} ${DUT_ip} platform_ImageLoaderServer

Change-Id: I4c9c93a33300c70b8078b79a4f1d03285968ee28
Reviewed-on: https://chromium-review.googlesource.com/446956
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Tested-by: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/60f1671508825c26e77bdacf2687d805da00fc0e/client/site_tests/platform_ImageLoader/platform_ImageLoader.py

Status: Fixed (was: Started)

Comment 4 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 5 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 6 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 7 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment