maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[MemProf] Reenable test with fix for bot failures 

The issue was unexpected macro expansion when the bot's test output
directory contained a token matching a build system macro (e.g.
"linux"). Switch to using a hardcoded path, which is invalid but is
sufficient for ensuring that the path is passed down to the runtime.

Differential Revision: https://reviews.llvm.org/D90466
This commit is contained in:
Teresa Johnson 2020-10-30 08:03:35 -07:00
parent 6b2de7c53a
commit 7f32ddc99b
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
compiler-rt/test/memprof/TestCases/log_path_test.cpp
View File

@ -19,11 +19,13 @@
// RUN: not %run %t 2>&1 | FileCheck %s --check-prefix=CHECK-LONG --dump-input=always
// Specifying the log name via the __memprof_profile_filename variable.
// Temporarily disable until bot failures fixed
// %clangxx_memprof %s -o %t -DPROFILE_NAME_VAR="%t.log2"
// rm -f %t.log2.*
// %run %t
// FileCheck %s --check-prefix=CHECK-GOOD --dump-input=always < %t.log2.*
// Note we use an invalid path since that is sufficient for checking that the
// specified __memprof_profile_filename value is passed through to the runtime.
// Using an automatically generated name via %t can cause weird issues with
// unexpected macro expansion if the path includes tokens that match a build
// system macro (e.g. "linux").
// RUN: %clangxx_memprof %s -o %t -DPROFILE_NAME_VAR="/dev/null/INVALID"
// RUN: not %run %t 2>&1 | FileCheck %s --check-prefix=CHECK-INVALID --dump-input=always
#ifdef PROFILE_NAME_VAR
#define xstr(s) str(s)