[perf] Add Bug ID display to V2 chart tooltip

This change implements the Bug ID display for the V2 performance
dashboard tooltip (`trace-chart-tooltip-sk`).

Key changes:
- Import formatBug from '../common/anomaly'.
- Add bug_host_url property to trace-chart-tooltip-sk, retrieving the
  URL from window.perf.bug_host_url.
- Conditionally render associated Bug ID as a clickable link in the
  tooltip.
- Hide the triage-menu-sk component when a bug is associated with the
  anomaly to prevent redundant actions.
- Update demo page configurations to include a valid bug_host_url.
- Update puppeteer tests to check bug ID rendering and verify the
  triage-menu-sk is hidden.

Bug: 519483919
Change-Id: I75abc8bcdd666601ce21d9a6108f29c18053c1ba
Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/1255558
Reviewed-by: Ruslan Schalkenbajew <sruslan@google.com>
Commit-Queue: Wenbin Zhang <wenbinzhang@google.com>
Auto-Submit: Wenbin Zhang <wenbinzhang@google.com>
3 files changed
tree: 476087a10533abf097cbabba8a386620253dd101
  1. .agents/
  2. am/
  3. android_ingest/
  4. android_stats/
  5. api/
  6. attest/
  7. autogardener/
  8. autoroll/
  9. bash/
  10. bazel/
  11. blamer/
  12. bugs-central/
  13. cabe/
  14. cbb/
  15. cd/
  16. cdn/
  17. cherrypick-watcher/
  18. cmd/
  19. codesize/
  20. comment_rag/
  21. comments/
  22. cq_watcher/
  23. ct/
  24. datahopper/
  25. debugger-app/
  26. demos/
  27. docker/
  28. docs/
  29. docsyserver/
  30. ds/
  31. elements-sk/
  32. external/
  33. fiddlek/
  34. firestore/
  35. get_service_account/
  36. gitsync/
  37. go/
  38. gold-client/
  39. golden/
  40. helloworld/
  41. infra/
  42. infra-sk/
  43. jsdoc/
  44. jsfiddle/
  45. k8s-checker/
  46. k8s-deployer/
  47. kube/
  48. leasing/
  49. licenses/
  50. machine/
  51. make/
  52. mcp/
  53. modules/
  54. named-fiddles/
  55. new_element/
  56. npm-audit-mirror/
  57. perdiff/
  58. perf/
  59. periodic-trigger/
  60. pinpoint/
  61. proberk/
  62. promk/
  63. puppeteer-tests/
  64. rag/
  65. sa-keys-checker/
  66. scrap/
  67. scripts/
  68. shaders/
  69. sk/
  70. skbug/
  71. skcq/
  72. skfe/
  73. skolo/
  74. skottie/
  75. static_server/
  76. status/
  77. task_driver/
  78. task_scheduler/
  79. temporal/
  80. test-service/
  81. tool/
  82. tools/
  83. tree_status/
  84. trybot_updater/
  85. .bazelignore
  86. .bazelrc
  87. .bazelversion
  88. .eslintrc.js
  89. .gitattributes
  90. .gitignore
  91. .golangci.yml
  92. .mockery.yaml
  93. .npmrc
  94. .prettierignore
  95. .prettierrc.json
  96. .puppeteerrc.js
  97. .pylintrc
  98. .swcrc
  99. .vpython
  100. BAZEL_CHEATSHEET.md
  101. BUILD.bazel
  102. build_infra_prod.sh
  103. CDB.md
  104. codereview.settings
  105. DATASTORE.md
  106. demopage.sh
  107. DEPS
  108. elements.d.ts
  109. go.mod
  110. go.sum
  111. karmatest.sh
  112. launch.md
  113. LICENSE
  114. LINT.md
  115. Makefile
  116. MODULE.bazel
  117. MODULE.bazel.lock
  118. OWNERS
  119. package-lock.json
  120. package.json
  121. pnpm-lock.yaml
  122. PRESUBMIT.py
  123. PRIVACY_POLICY.md
  124. puppeteerrc.bzl
  125. puppeteerrc.js.tpl
  126. README.md
  127. requirements.txt
  128. run_lint.sh
  129. STYLEGUIDE.md
  130. tools.go
  131. tsconfig.json
  132. whitespace.txt
  133. workflowcheck.yaml
README.md

Skia-Buildbot Repository

This repo contains infrastructure code for Skia.

Supported Infrastucture Platforms

The infrastructure code is generally built to run on x86 linux. Running on other platforms may be possible but is not officially supported and success will vary depending on the command.

Getting the Source Code

The main source code repository is a Git repository hosted at https://skia.googlesource.com/buildbot.git. It is possible to check out this repository directly with git clone or via go get.

Using git clone allows you to work in whatever directory you want. You will still need to set GOPATH in order to build some apps (recommended to put this in a cache dir). E.g.:

$ cd ${WORKDIR}
$ git clone https://skia.googlesource.com/buildbot.git
$ export GOPATH=${HOME}/.cache/gopath/$(basename ${WORKDIR})
$ mkdir $GOPATH
$ cd buildbot

Install dependencies

Almost all applications are built with Bazel, and bazelisk is the recommended tool to ensure you have the right version of bazel installed:

go install github.com/bazelbuild/bazelisk@latest
go install github.com/bazelbuild/buildtools/buildifier@latest
go install github.com/kisielk/errcheck@latest
go install golang.org/x/tools/cmd/goimports@latest
go install github.com/mikefarah/yq/v4@latest
go install go.chromium.org/luci/client/cmd/...@latest

Add bazelisk to path

export PATH=$PATH:$(go env GOPATH)/bin

Install Node.js and npm

You will need Node.js and npm installed to run web infrastructure tests and linters. We recommend using nvm to manage Node versions.

After installing Node.js, run the following command to install repository dependencies (including linter tools):

npm install

Install other dependencies:

sudo apt-get install jq

Build ~everything

bazelisk build --config=mayberemote //...

Test everything

Set up environ variables

This step might be an optional step, but some test requires these enviornment variables.

Runs

./scripts/run_emulators/run_emulators start

The following are example of environment variables.

Emulators started. Set environment variables as follows:
export DATASTORE_EMULATOR_HOST=localhost:8891
export BIGTABLE_EMULATOR_HOST=localhost:8892
export PUBSUB_EMULATOR_HOST=localhost:8893
export FIRESTORE_EMULATOR_HOST=localhost:8894
export COCKROACHDB_EMULATOR_HOST=localhost:8895

And stores these environment variables to ~/.bashrc file.

Execute tests

bazelisk test --config=mayberemote //...

Generated Code

To update generated code run the following in any directory:

go generate ./...

Running unit tests

Install Cloud SDK.

Use this command to run the presubmit tests:

./run_unittests --small

AI Code Review

Getting AI code review for a local commit:

bazelisk run //cmd/autoreview

Read more at cmd/autoreview/README.md