summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorMatthieu Baerts <matthieu.baerts@tessares.net>2022-03-09 22:16:31 +0300
committerJakub Kicinski <kuba@kernel.org>2022-03-10 23:29:58 +0300
commitc7d49c033de057b88398915b0eb2df2484dc8166 (patch)
tree92ca715f7db231bc04deb54de9ef1b8e35018bb0 /tools/perf/scripts/python/export-to-postgresql.py
parentae7bd9ccecc3495ff5c3692e100bdd9f0164e49d (diff)
downloadlinux-c7d49c033de057b88398915b0eb2df2484dc8166.tar.xz
selftests: mptcp: join: alt. to exec specific tests
Running a specific test by giving the ID is often what we want: the CI reports an issue with the Nth test, it is reproducible with: ./mptcp_join.sh N But this might not work when there is a need to find which commit has introduced a regression making a test unstable: failing from time to time. Indeed, a specific test is not attached to one ID: the ID is in fact a counter. It means the same test can have a different ID if other tests have been added/removed before this unstable one. Remembering the current test can also help listing failed tests at the end. Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net> Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions