<html>#2289: CT_MultiLevel tests abort when run using more than one thread via simfactory
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2019_10</td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Eloisa Bentivegna):</p>
<p>Thanks <span class="ap-mention" data-atlassian-id="557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22">@Roland Haas</span> , interesting I didn’t realize this earlier… I agree to revert the single-thread commit, and try getting some agreement with a more recent gcc. Also, the test obviously involves data which is very affected by roundoff, and this simply shouldn’t be the case. We have had recurring problems with this as any perturbation of any origin ends up showing up there. Perhaps it’s a matter of turning this into a more sensible test in the first place.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2289/ct_multilevel-tests-abort-when-run-using'>https://bitbucket.org/einsteintoolkit/tickets/issues/2289/ct_multilevel-tests-abort-when-run-using</a></p>
</html>