Clicking on one of the missing suites for a green build: http://cautotest-prod/afe/#tab_id=view_job&object_id=261338410

I can't see any information showing what happened 

The suite is being created with board:Nocturne, shouldn't be capitalized.

I would guess this is a regression in the build configuration

I don't know how the new build configs work, apparently there's a template file in Goldeneye somewhere?

Nice catch! 

See also https://buganizer.corp.google.com/issues/119774494

I tweaked the GE config so maybe it works now, but there's a tracking bug that says the GE model should be removed.

we need the result for R71-11151.40.0, but they are all missing:

https://stainless.corp.google.com/search?view=matrix&row=suite&col=build&first_date=2018-11-26&last_date=2018-11-28&suite=%5Ebvt%7C%5Epaygen&build=%5ER71-11151.40.0&board=%5Enocturne%24&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false

Any idea how to get them run and display in stainless?

You'll have to run the suites/tests that you need manually.  All suite scheduler does is run suites periodically.

Hi, this bug is blocking nocturne release deployment by the test team. Escalating as a P0.  If pushing shouldn't be blocked please advise so dchan@ and his team can unblock.

currently we have 8 bvt unit and 4 is repairing, 
8 under pool suites and 5 repair failed. 

+ayatane where is the repair log? and why the repair failed?

I think this might be a dupe of https://b.corp.google.com/issues/119774494 which should be fixed now. The tests seem to be coming out on the build this morning https://screenshot.googleplex.com/ncMe1WeadHy even if they are slow to come in.

Looking at the shard we have about 3 not really repairing for bvt.  Unfortunately we are out of "spare" DUTs to pull from.

Filed to manually repair
https://b.corp.google.com/issues/120212607

As to why it failed to automatically repair
http://chromeos-skunk-3.mtv.corp.google.com/results/hosts/chromeos6-row5-rack17-host17/1400408-repair/20182911083801/debug/autoserv.DEBUG

We seem to be getting tests, even if it is slowly, should this be closed?

Yes

[Auto-generated comment by a script] We noticed that this issue is targeted for M-72; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-72 label, otherwise remove Merge-TBD label. Thanks.