With this patch, a typical configuration for a builder using 'lnt runtest test-suite' to track performance
of code generated by LLVM could be:
{
'name': "builder-name", 'slavenames': ["slave-name"], 'builddir': "builder-builddir", 'factory': ClangBuilder.getClangCMakeBuildFactory( jobs=8, clean=False, checkout_compiler_rt=False, checkout_lld=False, test=False, useTwoStage=False, runTestSuite=True, env={'PATH':'/usr/lib/ccache:/usr/local/sbin:'+ '/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'}, testsuite_flags=['--cppflags', '-O3', '--threads=1', '--build-threads=8', '--use-perf=all', '--run-under', 'taskset -c 1', '--benchmarking-only', '--exec-multisample=3', '--exclude-stat-from-submission=compile'], extra_cmake_args=["-DLLVM_TARGETS_TO_BUILD='AArch64'", "-DLLVM_PARALLEL_LINK_JOBS=4"], submitURL='http://lnt.llvm.org/submitRun', testerName='LNT-AArch64-O3'), 'category': 'clang'
}
The only difference to using the somewhat deprecated 'lnt runtest nt'
is that a "testsuite_flags" parameter is defined instead of an
"nt_flags" parameter.
Could you throw an error or assert or something to make sure people don't pass in both nt_flags and testsuite_flags?