Add the IP group for us to edit, when there is a corresponding network access to the DUT, IP can be automatically selected so that the Dome/umpire can be properly connected.
Reported by
star....@quanta.corp-partner.google.com,
Nov 1 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Linux; Android 5.0.2; x600 Build/ABXCNOP5501304131S) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.83 Mobile Safari/537.36 Steps to reproduce the problem: In the production of Chrome device, the factory is likely to produce the same project in a number of production lines at the same time. Because of the limitations of the factory network architecture, each production line IP is different.The current new style factory bundle is not satisfactory, because the testing IP of SMT/FAT/RUNIN/FFT/GRT can not meet the needs of multiple IP. What is the expected behavior? Add the IP group for us to edit, when there is a corresponding network access to the DUT, IP can be automatically selected so that the Dome/umpire can be properly connected. What went wrong? IP can,t add a group and can't be select automatically. Did this work before? N/A Chrome version: Channel: n/a OS Version: Flash Version:
,
Nov 1 2017
Please make sure this is the right bugtracker for the bug report.
,
Nov 3 2017
Please file this in the right tracker, reply to this bug if you are unsure which bug tracker to use. |
|||
►
Sign in to add a comment |
|||
Comment 1 by eostroukhov@chromium.org
, Nov 1 2017Status: WontFix (was: Unconfirmed)