fix bug in writeLimeIldgLFN when using MPI.#41
Merged
edbennett merged 1 commit intoJun 12, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes an issue which meant ILDG configurations could not be written when using MPI.
Test_ildg_ioandTest_ildg_reducedfmt_iowere failing when launched withmpirun. ButTest_ildg_readwas passing.Tracing the callstack with
valgrind+gdbrevealedIldgWriter::writeLimeIldgLFNwas not confined to a single a MPI process. This meant multiple processes were trying to write the same Lime record and Lime was returning aLIME_ERR_PARAM. This is also broken upstream.I checked that all the ILDG related tests now work with
mpirunand with large lattices (including >4GB).