Reconcile differences between GoldenEye PFQ page and master-chromium-pfq's ScheduleSlaves output |
|||
Issue descriptionThe GoldenEye Chrome PFQ page at https://cros-goldeneye.corp.google.com/chromeos/console/listChromePfqBuild lists 14 boards for each build: chell cyan daisy-skate falco lumpy nyan peach-pit peppy reef tricky veyron-minnie veyron-pinky veyron-rialto x86-alex When I look at the output from the build master's ScheduleSlaves stage, e.g. https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fmaster-chromium-pfq%2F3940%2F%2B%2Frecipes%2Fsteps%2FScheduleSlaves%2F0%2Fstdout, I see 19 builders: amd64-generic-chromium-pfq arm-generic-chromium-pfq chell-chrome-pfq cyan-chrome-pfq daisy-chromium-pfq daisy_skate-chrome-pfq falco-chrome-pfq lumpy-chrome-pfq nyan-chrome-pfq peach_pit-chrome-pfq peppy-chrome-pfq reef-chrome-pfq tricky-chrome-pfq veyron_jerry-chromium-pfq veyron_minnie-chrome-pfq veyron_pinky-chrome-pfq veyron_rialto-chrome-pfq x86-alex-chrome-pfq x86-generic-chromium-pfq chell-chrome-pfq (which is listed by GoldenEye) and reef-chrome-pfq (which is not) are both experimental, per Steven, but what's the reason for the other discrepancies? Specifically, ScheduleSlaves lists amd64-generic, arm-generic, daisy, veyron_jerry, and x86-generic.
,
Feb 8 2017
,
Feb 8 2017
Are the -chrome-pfq builders all that need to pass for the master run to succeed, or do the -chromium ones need to pass as well? (Even if it's the latter, I assume/hope that they're compile-only and not failing often. I'll check this.)
,
Feb 8 2017
They do need to pass. A couple of them run VMTests. See this doc (which is at least partly out of date). There are columns for VMTests and HWTests. https://docs.google.com/spreadsheets/d/1Gdb2Rkfl7-RwhlHnrJ4-WxMTTWj5Dxp4wIueMn2vfnU/edit
,
Feb 9 2017
Thanks for the explanation! |
|||
►
Sign in to add a comment |
|||
Comment 1 by steve...@chromium.org
, Feb 7 2017