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

Issue 738528 link

Starred by 1 user
Status: Fixed
Owner:
█ krisr@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
Cc:
█ dshi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Consider adding adb host entries to the push to prod test instance

Reported by jrbarnette@chromium.org, Jun 30 2017 
Recently, testing of ADBHost objects broke, see
https://b.corp.google.com/issues/63074705 and bug 737316.

The bug wasn't found in testing for push to prod because
our test instance includes TestStations not ADB hosts.

We should consider adding the necessary Android DUTs to
the test instance to catch such problems.  Caveats/issues:
  * We'd need to obtain a permanent allocation of appropriate
    Android DUTs.
  * It's unlikely that the DUTs could/would live in Stierlin
    Ct, so we'd need someone other than englab-sys-cros@ to
    manage the DUTs.
  * CrOS Infra would need well-defined procedures for getting
    DUTs fixed promptly when there were problems.

Comment 1 by jrbarnette@chromium.org, Jun 30 2017

Owner: krisr@chromium.org
Status: Assigned (was: Available)
Passing to krisr@ to comment on the relative value/priority of
doing this, on the theory that he'd be responsible for providing
the DUTs.

Comment 2 by jrbarnette@chromium.org, Jun 30 2017

Cc: dshi@chromium.org
+dshi@, because he understands more about this than I do...

Comment 3 by dshi@chromium.org, Jun 30 2017 

krisr,

For lab to verify adb_host testing, we need a dedicated adb host from your lab, do you think you can spare one for test push purpose?

Comment 4 by krisr@chromium.org, Jun 30 2017 

Sure, we will get this done.

Comment 5 by krisr@chromium.org, Jun 30 2017 

Internal tracking: b/63176609

Comment 6 by jrbarnette@chromium.org, Jun 30 2017 

Wait, before this goes to far, we need some sort of minimal
SLO commitment, along the lines of "CrOS Infra can file a ticket
to get a fix or replacement for the devices, and obtain satisfaction
within 24 hours (or so)"  Otherwise, we'll just end up stopping
the testing, which would defeat the purpose.

Comment 7 by krisr@chromium.org, Jul 7 2017

Status: Fixed (was: Assigned)
New test station:
  android1758-row1-rack7-test-station-6

https://ubercautotest.corp.google.com/afe/#tab_id=view_host&object_id=5042

@comment6 we have an on-call lab person that is detailed here:
  https://sites.google.com/a/google.com/acs---android-comms-support---lab/team-info/monthly-support-responsibility?pli=1

If you ping the on-call person it will fix it that day.
►

Sign in to add a comment