I finally see why this test is failing (on now 2 bots). Somehow the path
name is getting messed up, and the "linux" converted to "1". I suspect
there is something in the environment causing the macro expansion in the
test to get messed up:
http://lab.llvm.org:8011/#/builders/112/builds/555/steps/5/logs/FAIL__MemProfiler-x86_64-linux__log_path_test_cpp
http://lab.llvm.org:8011/#/builders/37/builds/275/steps/31/logs/stdio
On the avr bot:
-DPROFILE_NAME_VAR="/home/buildbot/llvm-avr-linux/llvm-avr-linux/stage1/projects/compiler-rt/test/memprof/X86_64LinuxConfig/TestCases/Output/log_path_test.cpp.tmp.log2"
after macros expansions becomes:
/home/buildbot/llvm-avr-1/llvm-avr-1/stage1/projects/compiler-rt/test/memprof/X86_64LinuxConfig/TestCases/Output/log_path_test.cpp.tmp.log2
Similar (s/linux/1/) on the other bot.
Disable it while I investigate
// 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.
-// RUN: %clangxx_memprof %s -o %t -DPROFILE_NAME_VAR="%t.log2"
-// RUN: ls -l %T | FileCheck %s --dump-input=always
-// RUN: rm -f %t.log2.*
-// RUN: ls -l %T | FileCheck %s --dump-input=always
-// RUN: %run %t
-// RUN: FileCheck %s --check-prefix=CHECK-GOOD --dump-input=always < %t.log2.*
+// 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.*
#ifdef PROFILE_NAME_VAR
#define xstr(s) str(s)
// CHECK-GOOD: Memory allocation stack id
// CHECK-INVALID: ERROR: Can't open file: /dev/null/INVALID
// CHECK-LONG: ERROR: Path is too long: 01234
-// CHECK: log_path_test