ppc64le front end launcher fix and el cap host profile #20123
Merged
Conversation
This file contains 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
biagas
previously approved these changes
Dec 12, 2024
cyrush
added a commit
that referenced
this pull request
Dec 13, 2024
* ppc64le front end launcher fix and el cap host profile * change el cap launch configs to use 96 cores (targets 5gb of ram per core)
cyrush
added a commit
that referenced
this pull request
Dec 13, 2024
|
Thanks for fixing the |
|
No worries -- Looking at Mark's PR for macOS I realized the number of places we have to provide the arch is surprising, I created a ticket to discuss: |
1 similar comment
|
No worries -- Looking at Mark's PR for macOS I realized the number of places we have to provide the arch is surprising, I created a ticket to discuss: |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Description
Type of change
How Has This Been Tested?
Reminders:
Checklist:
- [ ] I have commented my code where applicable.- [ ] I have updated the release notes.- [ ] I have made corresponding changes to the documentation.- [ ] I have added debugging support to my changes.- [ ] I have added tests that prove my fix is effective or that my feature works.- [ ] I have confirmed new and existing unit tests pass locally with my changes.- [ ] I have added new baselines for any new tests to the repo.