<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Two ASAN tests sensitive to '@' in path name"
href="https://bugs.llvm.org/show_bug.cgi?id=33658">33658</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Two ASAN tests sensitive to '@' in path name
</td>
</tr>
<tr>
<th>Product</th>
<td>new-bugs
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>new bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>paul_robinson@playstation.sony.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>(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):
--
/usr/bin/ld:
/home/siadmin/jenkins/w/opensource/opensource_build@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@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
invocation)
We have finally determined that the problem is that Jenkins sometimes
likes to put '@2' into a pathname, hence the 'opensource_build@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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>