commit | 71f934b2caf077b3638d4ee8bbebc12503ad624f | [log] [tgz] |
---|---|---|
author | Kyle Ju <kyleju@chromium.org> | Tue Aug 11 16:17:41 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Aug 11 16:17:41 2020 |
tree | 5f4dcdcc48f43ff82da21edc010485f8dd0ccfb6 | |
parent | 86ae1baf570efa38f7ca9251586579faa231c871 [diff] |
[Export Notifier] Migrate to the GitHub Check Suites API from the Status API Testing Command: python third_party/blink/tools/wpt_export.py --dry-run --credentials <your credentials> --surface-failures-to-gerrit --verbose A Sample Comment: The exported PR, https://github.com/web-platform-tests/wpt/pull/24650, has failed the following check(s) on GitHub: wpt-firefox-nightly-stability (https://github.com/web-platform-tests/wpt/pull/24650/checks?check_run_id=883668859) ... These failures will block the export. They may represent new or existing problems; please take a look at the output and see if it can be fixed. Unresolved failures will be looked at by the Ecosystem-Infra sheriff after this CL has been landed in Chromium; if you need earlier help please contact ecosystem-infra@chromium.org. Gerrit CL SHA: 0e4d176d93a1a70e03720dbeb8142139e0df5871 Patchset Number: 2 Change-Id: I3376a7913c6677ed219717d2a4ddbc065ce83fbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336542 Commit-Queue: Kyle Ju <kyleju@chromium.org> Reviewed-by: Robert Ma <robertma@chromium.org> Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#796851}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.