Find
C
ase-sensitive
R
egexp search
Path
Showing
18d9efd5
from
2026-09-25
:
Revert "Bug
2075271
, Bug
2075001
, Bug
2066245
, Bug
2074974
, Bug
2066247
, Bug
2066248
, Bug
2066246
, Bug
2066244
, Bug
2066242
, Bug
2066240
, Bug
2066236
- Stub the widget market prefs in newtab for older hosts r=thecount" for causing marionette integration tests failures at test_backup.py
firefox-main
/
third_party
/
libwebrtc
/
tools_webrtc
/
perf
Navigation
Enable keyboard shortcuts
Name
Description
Size
Coverage
BUILD.gn
624
-
catapult_uploader.py
Required information to upload perf metrics. Attributes: perf_dashboard_machine_group: The "master" the bots are grouped under. This string is the group in the the perf dashboard path group/bot/perf_id/metric/subtest. bot: The bot running the test (e.g. webrtc-win-large-tests). test_suite: The key for the test in the dashboard (i.e. what you select in the top-level test suite selector in the dashboard webrtc_git_hash: webrtc.googlesource.com commit hash. commit_position: Commit pos corresponding to the git hash. build_page_url: URL to the build page for this build. dashboard_url: Which dashboard to use. input_results_file: A HistogramSet proto file coming from WebRTC tests. output_json_file: Where to write the output (for debugging). wait_timeout_sec: Maximum amount of time in seconds that the script will wait for the confirmation. wait_polling_period_sec: Status will be requested from the Dashboard every wait_polling_period_sec seconds.
10792
-
catapult_uploader_test.py
4705
-
process_perf_results.py
Adds build info to perf results and uploads them. The tests don't know which bot executed the tests or at what revision, so we need to take their output and enrich it with this information. We load the proto from the tests, add the build information as shared diagnostics and then upload it to the dashboard. This script can't be in recipes, because we can't access the catapult APIs from there. It needs to be here source-side.
4598
-
process_perf_results_test.py
2624
-