commit | 218c2a7d5374a4848bc79f309324850f6b40f0a6 | [log] [tgz] |
---|---|---|
author | Takuto Ikuta <tikuta@chromium.org> | Thu Dec 13 06:06:51 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Dec 13 06:06:51 2018 |
tree | 3f0165ce3045707a685af6e536c3f6a7bdf8618a | |
parent | def42bb00d63fd1eaa379e64949bc12adb49df51 [diff] |
[chromium] use output property to detect confirm no-op failure Currently WARNING status is not supported in BigQuery table. Instead, I was told that we can use property to detect unexpected failure in https://bugs.chromium.org/p/chromium/issues/detail?id=914268#c6 I will use this property to collect confirm no-op failure steps. Bug: 914264 Change-Id: Ic5ae309831b502ce53896a56555f8ed81c39b08a Reviewed-on: https://chromium-review.googlesource.com/c/1375550 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Shinya Kawanaka <shinyak@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Hi build contributor! If you do any change in scripts/master/
or touching any master's html/
directories, you must restart master.chromium.fyi first and ensure that it still works before restarting other masters.
If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*
), please take a look at the README for more information pertaining to recipes.