CQ attempts data seems wrong |
|||
Issue descriptionRunning the query "SELECT issue, patchset, click_to_result_sec FROM chrome_infra.cq_attempts WHERE issue = '773700';" gives me this: issue patchset click_to_result_sec 773700 2 164083.223 773700 2 26.131 Which makes it seem like the patchset took 45 hours to get a result. https://chromium-cq-status.appspot.com/v2/patch-status/chromium-review.googlesource.com/773700/2 makes it look like it only took an hour. Not sure what's going on here....
,
Nov 22 2017
Stephen, is this BQ-sourced data? I suspect this is because there were two attempts: First: Mon Nov 20 2017 05:12:35 GMT-0800 (PST)(10 seconds) CQ stopped processing patch (Dry run: only full committers or CL owner with tryjob access are allowed to trigger CQ dry run) Second finished OK: Wed Nov 22 2017 02:42:30 GMT-0800 (PST)(1 hour) CQ stopped processing patch So, here you get 45 hours, which implies a bug in cq_attempts table calculation from raw data.
,
Nov 23 2017
This is data is in dremel, not bigquery. Your explanation makes sense.
,
Jul 1
|
|||
►
Sign in to add a comment |
|||
Comment 1 by katthomas@google.com
, Nov 22 2017Components: -Infra>Monitoring Infra>Platform>CQ