feat(linux): set unlimited stack size for SPEC runtime scripts - #58
Merged
Conversation
Contributor
|
I found one minor issue in the SPEC2017 packaging script: write_runtime_files() already emits |
Contributor
Author
Good catch — it was indeed a duplicate. I removed the newly added line (previously at line 925) from write_runtime_files() and kept the existing |
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
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.
ulimit -s unlimited 2>/dev/null || trueto therun.shgenerated by the three packaging scripts for spec2006 / spec2017 / spec2026, setting the stack limit to unlimited at script startup to reduce the risk of run failures caused by the default stack limit.write_runtime_files/generate_runtime_script).2>/dev/null || trueensures the script continues executing even if the ulimit adjustment fails or the environment isrestricted, so it is not affected by
set -e.