Android devices treated as cros through AFE |
|||||||||||
Issue description<b>Chrome Version : <Copy from: 'about:version'></b> URLs (if applicable) : Other browsers tested: Chrome: Fail Steps to reproduce: (1) Create a test job through the AFE for any android device, image version does not matter. Look at the link above for example if needed. (2) Submit the job (3) Look at dependencies on queued job, it should say cros-version: followed by the android image you entered. Expected result: Test provisions as android device. Actual result: Test tries to provision as a cros device. Please provide any additional information below. Attach a screenshot if possible. b/34251817
,
Jan 12 2017
,
Jan 12 2017
Simran, I think this is what your team is building.
,
Jan 12 2017
1) go to here http://chromeos-autotest.hot.corp.google.com/afe/ 2) click create job 3) Enter any name for the test name 4) Enter git_oc-release/aosp_shamu-userdebug/3629397 as image 5) Select android_ACTS:SampleTest for test 6) Select android1758-row1-rack7-test-station-7.cros for host 7) Submit job 8) Dependencies on new job should read cros-version:git_oc-release/aosp_shamu-userdebug/3629397 9) Job should fail during provisioning This only happens through the AFE, not through command line or with suite jobs.
,
Jan 12 2017
Can you send me some links on jobs, how long has it been broken?
,
Jan 12 2017
Richard's CL broke this functionality in that it assumes we only do Chrome OS testing... Richard I suggest looking at the run_suite code for how to determine the appropriate build prefix. https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/site_utils/run_suite.py#1528 Theres a prefix for Android and for Testbed. https://chromium-review.googlesource.com/#/c/423389/ +Don/KrisR as I don't think this is deployed to cautotest proper yet. We may want to revert the CL if this impacts KrisR's team.
,
Jan 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/a06ea083f536d8bf755be9356dba66a369bb9ab2 commit a06ea083f536d8bf755be9356dba66a369bb9ab2 Author: Don Garrett <dgarrett@chromium.org> Date: Fri Jan 13 00:04:26 2017 Revert "[autotest] Use provisioning in place of parameterized jobs." This reverts commit ca14cc94db12a404c840ebb4b8e8dffe66245e3c. BUG= chromium:680656 Change-Id: Ic596fb29e15c4a9309e099c83ab36723131d8743 Reviewed-on: https://chromium-review.googlesource.com/427999 Reviewed-by: Simran Basi <sbasi@chromium.org> Commit-Queue: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> [modify] https://crrev.com/a06ea083f536d8bf755be9356dba66a369bb9ab2/frontend/afe/rpc_interface.py
,
Jan 17 2017
,
Jan 17 2017
The revert should have made this go away. We'll have to do more work to make a proper fix for bug 628694.
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by dshi@chromium.org
, Jan 12 2017