New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 640415 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
█ kevcheng@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Servo V4 will break test_that using servo in the lab

Reported by jrbarnette@chromium.org, Aug 23 2016 
See bug 640405 for a sample of the use case in question.

When using `test_that` against a DUT in the lab, if the test
requires servo, the current create_servo_host() finds the servo
host by magic.  That magic will quit working with servo V4.

There's a workaround in the form of "require users to pass in
the servo host and port number", but that workaround is likely
to annoy users beyond their ability to bear.  So, we want to
find a better solution.

Comment 1 by kevcheng@chromium.org, Aug 24 2016 

quick'n'dirty fix: Send a quick call to the AFE (no retries and times out in 1 sec) to grab host attributes and pass them through.

long-term fix (per Richard): Provide a stub AFE at least for hosts and bury it in the 'job' object in Host.job and provide a config file for manually specifying host information.

Comment 2 by aut...@google.com, Aug 30 2016

Owner: kevcheng@chromium.org

Comment 3 by dchan@chromium.org, Oct 26 2016

Labels: servov4

Comment 4 by kevcheng@chromium.org, Jun 5 2017 

Issue 729650 has been merged into this issue.

Comment 5 by kevcheng@chromium.org, Jun 5 2017 

the args to pass in would be "servo_host" and "servo_port" (just for anyone who needs the workaround now).

Comment 6 by akes...@chromium.org, Mar 31 2018

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>Test
Labels: -Pri-2 Pri-3

Comment 7 by akes...@chromium.org, Mar 31 2018

Owner: a-...@yandex-team.ru

Comment 8 by akes...@chromium.org, Mar 31 2018

Owner: ----
►

Sign in to add a comment