aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetLoweringBase.cpp
diff options
context:
space:
mode:
authorRainer Orth <ro@gcc.gnu.org>2025-02-11 09:02:05 +0100
committerGitHub <noreply@github.com>2025-02-11 09:02:05 +0100
commita0587414cbb1520cfd7e886de1d18c408539ac9f (patch)
tree27c14ab4ed78252415765b4d954f84441d70e61b /llvm/lib/CodeGen/TargetLoweringBase.cpp
parent7af4ab4f072ee6de9d347f9955683d4a49645f1c (diff)
downloadllvm-a0587414cbb1520cfd7e886de1d18c408539ac9f.zip
llvm-a0587414cbb1520cfd7e886de1d18c408539ac9f.tar.gz
llvm-a0587414cbb1520cfd7e886de1d18c408539ac9f.tar.bz2
[sanitizer_common][test] Remove second SanitizerCommon.ReportFile tem… (#126509)
…p file The `SanitizerCommon.ReportFile` test leaves a temp file behind on every run. While this is not a problem for manual builds, on buildbots those files accumulate over time, interfering with other bots on the same system. The files in question are named like `sanitizer_common.reportfile.tmp.XXXXXX.<pid>`. The issue can be seen in Solaris `truss` output: ``` 22633: fstatat64(AT_FDCWD, "/tmp/sanitizer_common.reportfile.tmp.rzVEja", 0xFEFFBAD0, AT_SYMLINK_NOFOLLOW) Err#2 ENOENT 22633: openat64(AT_FDCWD, "/tmp/sanitizer_common.reportfile.tmp.rzVEja", O_RDWR|O_CREAT|O_EXCL, 0600) = 3 22633: openat64(AT_FDCWD, "/tmp/sanitizer_common.reportfile.tmp.rzVEja.22633", O_WRONLY|O_CREAT|O_TRUNC, 0660) = 4 22633: unlinkat(AT_FDCWD, "/tmp/sanitizer_common.reportfile.tmp.rzVEja", 0) = 0 ``` The first temp file, created by `temp_file_name`, is removed at the end of the test, the second one, created in `ReportFile::GetReportPath` using `OpenFile`, is not. This patch fixes this, simply removing the file. Tested on `amd64-pc-solaris2.11` and `x86_64-pc-linux-gnu`.
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringBase.cpp')
0 files changed, 0 insertions, 0 deletions