aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/VirtualFileSystem.cpp
diff options
context:
space:
mode:
authorDavid Spickett <david.spickett@linaro.org>2024-10-21 10:43:45 +0100
committerGitHub <noreply@github.com>2024-10-21 10:43:45 +0100
commit8507dbaec3f644b8a0c6291f097800d82a4f4b16 (patch)
treee713eac842e8b747e9459e955c56d4f752199440 /llvm/lib/Support/VirtualFileSystem.cpp
parent4f06f79c03f8392f63f4430fcfcaefa763cf5c93 (diff)
downloadllvm-8507dbaec3f644b8a0c6291f097800d82a4f4b16.zip
llvm-8507dbaec3f644b8a0c6291f097800d82a4f4b16.tar.gz
llvm-8507dbaec3f644b8a0c6291f097800d82a4f4b16.tar.bz2
[llvm][llvm-lit] Add option to create unique result file names if results already exist (#112729)
When running a build like: ``` ninja check-clang check-llvm ``` Prior to my changes you ended up with one results file, in this specific case Junit XML: ``` results.xml ``` This would only include the last set of tests lit ran, which were for llvm. To get around this, many CI systems will run one check target, move the file away, then run another, somehow propgating the return code as well. ``` rectode=0 for target in targets: ninja target retcode=$? mv results.xml results-${target}.xml <report the overall return code> ``` I want to use something like this Buildkite reporting plugin in CI, which needs to have all the results available: https://buildkite.com/docs/agent/v3/cli-annotate#using-annotations-to-report-test-results Modifying CI's build scripts for Windows and Linux is a lot of work. So my changes instead make lit detect an existing result file and modify the file name to find a new file to write to. Now you will get: ``` results.xml results.<tempfile generated value>.xml ``` This will work for all result file types since I'm doing it in the base Report class. Now you've got separate files, it's easy to collect them with `<path>/*.xml`. Note that the `<tempfile generated value>` is not ordered.
Diffstat (limited to 'llvm/lib/Support/VirtualFileSystem.cpp')
0 files changed, 0 insertions, 0 deletions