FDS Build: Test GitHub actions memory for linux. #13930
Merged
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
FDS Build: Test GitHub actions memory FDS Build: Test GitHub actions memory FDS Build: Test GitHub actions memory FDS Build: Test GitHub actions memory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Marcos and I found that during the linking phase, the intel release solver may require 1.5–2 GB of heap memory. I am adding an additional command, ulimit -a, which will print out the available memory on Ubuntu systems before starting the Debug and Release builds. This might help to identify whether the infrequent 'malloc' errors during the release build has anything to do with the system memory.