The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/c16e4c4c18e3837081e137896977fa127ca96fb7

commit c16e4c4c18e3837081e137896977fa127ca96fb7
Author: Jacob Dufault <jdufault@google.com>
Date: Thu Nov 01 21:21:28 2018

chromeos_config: Mark tricky-chrome-pfq as experimental

BUG= chromium:901046 
TEST=inspect generated output

Change-Id: I730fdafcf783a40204d58b7b7cb3ae903616091c
Reviewed-on: https://chromium-review.googlesource.com/1313288
Commit-Ready: Jacob Dufault <jdufault@chromium.org>
Tested-by: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Alex Zamorzaev <zamorzaev@chromium.org>

[modify] https://crrev.com/c16e4c4c18e3837081e137896977fa127ca96fb7/config/chromeos_config.py
[modify] https://crrev.com/c16e4c4c18e3837081e137896977fa127ca96fb7/config/config_dump.json

I'm a bit concerned about us using "experimental" for flaky boards that are not actually new or experimental. We can always manually uprev a PFQ run if it was due to one or more flaky boards.

Can we make sure that issues are filed for each failure?

If a specific DUT is failing we need to file an issue to have that DUT removed. The last three failures all appear to have been on chromeos4-row2-rack4-host1 (which is not clear in the 'Build Health' page, I noticed by clicking on [Test Logs] for each failure).

Hi stevenjb@,

I am preparing cls to remove the experimental tags for tricky and other boards as well.

For this particular cl for tricky, should I revert this cl in #1 or create another cl to remove the experimental.

Thanks.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/ffec6a8edd6839db54601302c347ee1414e18abd

commit ffec6a8edd6839db54601302c347ee1414e18abd
Author: wutao <wutao@chromium.org>
Date: Fri Nov 09 17:36:02 2018

Make tricky-chrome-pfq important

tricky-chrome-pfq is green. Make it important.

BUG= chromium:901046 
TEST=inspect generated output

Change-Id: Ia0cf138f8905de79cb1c0da2a66ee2287f4ed3e4
Reviewed-on: https://chromium-review.googlesource.com/1327628
Commit-Ready: Tao Wu <wutao@chromium.org>
Tested-by: Tao Wu <wutao@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Alex Zamorzaev <zamorzaev@chromium.org>

[modify] https://crrev.com/ffec6a8edd6839db54601302c347ee1414e18abd/config/chromeos_config.py
[modify] https://crrev.com/ffec6a8edd6839db54601302c347ee1414e18abd/config/config_dump.json