... | ... | @@ -97,6 +97,11 @@ Upon failing some performance tests, the test runner will output the string req |
|
|
|
|
|
CAUTION: make sure you maintain the correct expected changes in your commit messages when squashing commits.
|
|
|
|
|
|
You probably don't want to use the `test_env` and `way` options because it can be tricky knowing all the `test_env`s and
|
|
|
`way`s that the commit will be checked under. The regular MR pipeline, the marge-bot pipeline, the nightly pipeline, and
|
|
|
any pipelines for older branches if the commit is backported are all likely to have different `test_env` names, so it is
|
|
|
often better to just accept changes for all `test_env`s and `way`s rather than trying to be selective.
|
|
|
|
|
|
## Comparing Commits
|
|
|
|
|
|
There exists a comparison tool located at `testsuite/driver/perf_notes.py` to help analyze the performance metrics commits. Run the commandline `testsuite/driver/perf_notes.py --help` to see the available options. E.g. to see a chart of the last 100 commits as a standalone html file (omit `--chart` to get simple text output to `stdout`):
|
... | ... | |