| OLD | NEW |
|---|
| (Empty) | |
| 1 The code is this directory is neither endorsed nor supported by the Chromium |
| 2 benchmarking team. |
| 3 |
| 4 To add code in this directory: |
| 5 1. First check the list of available benchmarking harnesses at |
| 6 bit.ly/chrome-benchmark-harnesses and make sure that your use case cannot fit |
| 7 any of the supported harness. If there is a related harness, please reach out |
| 8 to us and extend existing functionality. |
| 9 2. If your test case cannot fit into any existing harness, create a |
| 10 sub-directory with yourself and at least one another person as the OWNERS. Send |
| 11 the CL containing ONLY the new OWNERS file to the owners of tools/perf/. Your |
| 12 CL description should describe what the code you plan to add do. If it's an |
| 13 ephemeral benchmark used to drive a perf project, you need an accompanied bug |
| 14 (assigned to you) to clean up the benchmarks once your perf project is launched. |
| 15 |
| 16 **NOTE** |
| 17 1. Benchmarks in this directory will not be scheduled for running on the |
| 18 perf waterfall. |
| 19 2. Chromium benchmarking team will NOT review nor maintain any code under this |
| 20 directory. It is the responsiblity of the owners of each sub-directory to |
| 21 maintain them. |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2827393002:
Create tools/perf/contrib directory (Closed)
