• Home
Name Date Size #Lines LOC

..--

code_coverage/04-Jul-2025-2,7472,164

PRESUBMIT.pyD04-Jul-2025688 2211

README.mdD04-Jul-2025635 1611

common_merge_script_tests.pyD04-Jul-20251.5 KiB5741

merge_api.pyD04-Jul-2025833 2315

noop_merge.pyD04-Jul-20251,016 4327

noop_merge_test.pyD04-Jul-20252.2 KiB7245

perf_results.pyD04-Jul-2025430 178

results_merger.pyD04-Jul-20258.4 KiB272173

results_merger_test.pyD04-Jul-20258.2 KiB287238

standard_gtest_merge.pyD04-Jul-20256.7 KiB198137

standard_gtest_merge.pydepsD04-Jul-2025226 54

standard_gtest_merge_test.pyD04-Jul-202518.8 KiB599532

standard_isolated_script_merge.pyD04-Jul-20253.1 KiB10475

standard_isolated_script_merge.pydepsD04-Jul-2025274 65

standard_isolated_script_merge_test.pyD04-Jul-20255.1 KiB185139

README.md

1# Swarming merge scripts
2
3This directory contains Swarming merge scripts. Merge scripts run to collect the
4results of a swarming run of a test suite. Their basic operation is to merge
5together test results from the shard runs. They can also perform other post
6processing steps, such as uploading some test results to another test result
7server.
8
9There are a few merge scripts here which are simple wrappers around other
10scripts. These exist just so that every merge script we know about lives in a
11centralized location.
12
13Merge scripts are documented here:
14
15https://cs.chromium.org/search/?q=file:swarming/api.py+%22*+merge:%22&type=cs
16