CQ bot linux_layout_tests_slimming_paint_v2 is very slow |
|||
Issue descriptionhttps://build.chromium.org/p/tryserver.chromium.linux/builders/linux_layout_tests_slimming_paint_v2 A CQ job on linux_layout_tests_slimming_paint_v2 normally finishes in about 30 minutes, but currently two jobs seem to block the CQ: 6624 ETA: 13:44:27 [13 mins, 39 secs] [Running for: 2 hrs, 27 mins, 51 secs] webkit_layout_tests (without patch) 6625 ETA: 13:52:21 [21 mins, 34 secs] [Running for: 1 hrs, 48 mins, 59 secs] webkit_layout_tests (without patch)
,
Sep 27 2017
,
Sep 27 2017
Please, file general bugs abotu CHrome CQ against Infra>Client>Chrome in the future. Thanks!
,
Sep 27 2017
,
Sep 27 2017
Actually I still don't know what the difference between "general bugs about Chrome CQ" and "issues the backend handling commit queue requests handled by the Chrome OPs foundation team" is. Is there some document with examples explaining this?
,
Sep 27 2017
if am not aware of a high level doc, so instead I'd recommend to Infra>Client>Chrome since it's general, while CQ backend is very specific.
,
Sep 27 2017
The description of Infra>Platform>CQ and comments like #c4 in this bug seem not to prevent developers from filing CQ problem bugs to it. Perhaps we should add a new component Infra>Client>Chrome>CQ for bugs of CQ problems.
,
Sep 28 2017
Re #8. Just updated the Infra>Client>Chrome component description with "CQ" in the text so monorail search will present Infra>Client>Chrome when "cq" is typed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by wangxianzhu@chromium.org
, Sep 27 2017