[results.html] Support ResultDB

If ?json=<full_results_jsonp.js URL>&build_id=<build_bucket_id> is
specified in the results.html URL, we'll load full_results_jsonp.js
from the specified location (instead of from the same directory), and
fetch test artifact URLs from ResultDB. On startup, we'll fetch all
artifacts for tests with unexpected failures in batches asynchronously
and cache the result. If a test is expanded before the cache is ready or
the test is not included in the cache (e.g. the test didn't fail
unexpectedly), we'll fetch artifact URLs for the test with a dedicated
asynchronous request.

If there is only ?json=<full_results_jsonp.js URL> without build_id,
we'll load the specified full_results_jsonp.js and set the base URL
to the directory, assuming all artifacts are under the same directory.

Rebaseline script won't work in the ResultDB mode. We have added a
warning, and will probably remove the feature after we fully switch to
ResultDB.

To test, you can open the following URL:
.../results.html?json=https://chromium-layout-test-archives.storage.googleapis.com/mac10_13-blink-rel/18068/blink_web_tests%20%28with%20patch%29/full_results_jsonp.js&build_id=8796098237407454705

Bug: 1382949
Change-Id: Ibed27f7e83ff8f5bdb239ee1958d8ad396dc5314
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4068051
Reviewed-by: Weizhong Xia <weizhong@google.com>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1077834}
1 file changed
tree: 879100ded2b654bb0d15ea7372e7ecdf4d6748ed
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

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.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

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.

If you found a bug, please file it at https://crbug.com/new.