[llvm-bugs] [Bug 33658] New: Two ASAN tests sensitive to '@' in path name
llvm-bugs at lists.llvm.org
Fri Jun 30 08:46:03 PDT 2017
Bug ID: 33658
Summary: Two ASAN tests sensitive to '@' in path name
OS: Windows NT
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: paul_robinson at playstation.sony.com
CC: llvm-bugs at lists.llvm.org
(I'm not aware of a 'sanitizer' product so I put this in new-bugs.)
We recently went through some head-banging over this:
Failing Tests (2):
AddressSanitizer-x86_64-linux :: TestCases/Linux/local_alias.cc
AddressSanitizer-x86_64-linux :: TestCases/Linux/odr-violation.cc
which occurred only on our build machine, nobody could repro locally.
The specific error came from ld:
Command Output (stderr):
/home/siadmin/jenkins/w/opensource/opensource_build at 2/build/projects/compiler-rt/test/asan/X86_64LinuxConfig/TestCases/Linux/Output/local_alias.cc.tmp-INSTRUMENTED-SO.so:
version node not found for symbol
h/home/siadmin/jenkins/w/opensource/opensource_build at 2/llvm/projects/compiler-rt/test/asan/TestCases/Linux/local_alias.cc
/usr/bin/ld: failed to set dynamic section sizes: Bad value
clang-5.0: error: linker command failed with exit code 1 (use -v to see
We have finally determined that the problem is that Jenkins sometimes
likes to put '@2' into a pathname, hence the 'opensource_build at 2' part
of the pathname that ld is complaining about. I'm told this is something
Jenkins likes to do when you have concurrent builds enabled, and sometimes
even when you don't. :-P
We've restarted our Jenkins so it won't do that, at least for now.
But it would be nice if these tests didn't fail for environmental reasons.
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-bugs