cros tryjob --hwtest does not run chrome-informational suite |
|||
Issue descriptionWhile attempting to bisect a failure in the chrome-informational suite, I ran: cros tryjob eve-tot-chrome-pfq-informational-tryjob --notest --hwtest --chrome_version 7fa1000f175eeb5e0ee75287ab8c69feb13fdd2d Expecting that it would run the chrome-informational suite that normally runs on eve-tot-pfq-informational. Unfortunately, other HWTest suites were run, but not chrome-informational: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8927213308983574048
,
Dec 14
Over to oncall.
,
Dec 14
I'm a bit confused. Is this a feature request to run only HW tests when you pass both the --notest and --hwtest flags?
,
Dec 14
No (although that would also be nice). This is a request to have --hwtest run the chrome-informational HWTest suite on pfq-informational-tryjob builders.
,
Dec 14
Do the pfq-informational builders run them today? If so, then the -tryjob variants should as well.
,
Dec 14
Yes, they do, e.g.: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8927243951180508896 The stage is "HWTest [chrome-informational]" It runs FYI tests, currently Tast tests and Mash autotests. We do not run the chrome-informational suite in the PFQ itself, so it's possible that is part of the problem. |
|||
►
Sign in to add a comment |
|||
Comment 1 by steve...@google.com
, Dec 14