<html>#2598: thornyflat - production run segmentation fault
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Maria</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2021_11</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Comment (by Maria):</p>
<p>Sure, no problem! Meantime, I still want to be able to run ETK on ThornyFlat. Anuj, what version of mpi/gcc are you using when you were able to run on ThornyFlat? </p>
<p>I was on the phone with Guillermo and Patrick for 2 hours Today. Apparently I have the same rights to compute nodes as any WVU faculty on ThornyFlat community nodes supported by NSF. It’s not the memory or access, although ThornyFlat was rather slow Today. The problem was tracked down to a bug that seems to appear when mpi4.1 talks with gcc11. It is not fixed yet. I am to try to use instead gcc3.1.6 and report back. They’ll work on their end to figure out if it’s fixable by them, or it’s a bug in mpi4.1 that must be reported. As for me not being able to send tickets, this seem to be managed by a different team, that I have to contact.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-production-run-segmentation'>https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-production-run-segmentation</a></p>
</html>