Not all the boards pick the same version when scheduling FAFT |
||
Issue descriptionCheck the dashboard: http://go/faft_bios_dashboard The snapshot: https://screenshot.googleplex.com/PAMZegRDtzb FAFT BIOS suite is scheduled nightly. Given the 6/13 result as an example, most of the boards picked the test version R53-8446.0.0; however, some boards, e.g. celes and veyron_mickey, picked the different test version R53-8444.0.0. All boards should pick the same test version such that we can see a consistent result.
,
Jun 20 2016
The suite scheduler pulls the latest "good" ChromeOS build to run test: [FaftBiosNightly] run_on: nightly hour: 16 suite: faft_bios branch_specs: ==tot firmware_ro_build_spec: firmware test_source: cros pool: faft-test file_bugs: True job_retry: True tot here doesn't mean the latest build, it has to be a good build. As an example, https://ubercautotest.corp.google.com/afe/#tab_id=view_job&object_id=67127407 https://ubercautotest.corp.google.com/afe/#tab_id=view_job&object_id=67127217 For cyan, 8466 is bad, and 8464 is good, so the suite job uses build 8464 For auron_paine, 8466 is good, so it's used.
,
Jun 21 2016
Thanks for explanation. Is it possible to group the result per day, like using another view flag? It makes sense to view the nightly suite in this view. Together with the issue 608412 , the current layout is difficult to understand. Can't easy to figure out if the missing result is caused by bad build or other reason. |
||
►
Sign in to add a comment |
||
Comment 1 by waihong@chromium.org
, Jun 20 2016