Name Date Size #Lines LOC

..--

code_coverage/H25-Apr-2025-2,6352,073

PRESUBMIT.pyH A D25-Apr-2025687 2011

README.mdH A D25-Apr-2025635 1611

common_merge_script_tests.pyH A D25-Apr-20251.5 KiB5338

merge_api.pyH A D25-Apr-2025789 2113

noop_merge.pyH A D25-Apr-20251 KiB4629

noop_merge_test.pyH A D25-Apr-20252.3 KiB7449

perf_results.pyH A D25-Apr-2025428 178

results_merger.pyH A D25-Apr-20258.5 KiB285185

results_merger_test.pyH A D25-Apr-20257.8 KiB297244

standard_gtest_merge.pyH A D25-Apr-20256.6 KiB203140

standard_gtest_merge.pydepsH A D25-Apr-2025226 54

standard_gtest_merge_test.pyH A D25-Apr-202517.1 KiB617544

standard_isolated_script_merge.pyH A D25-Apr-20253.1 KiB10677

standard_isolated_script_merge.pydepsH A D25-Apr-2025274 65

standard_isolated_script_merge_test.pyH A D25-Apr-20255 KiB189148

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