26040: Detect compute limitations/configurations - MINOR - #737
Merged
Merged
Conversation
apbassett
approved these changes
Sep 22, 2026
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.
Add checks for situations where the available compute may be different than accessible compute and CPU affinity/visibility checks to
installation_verification. These are always warnings, never errors and are meant to head off complicated diagnosis of poor performance caused by customer hardware configurations.main. The supported interfaces are unchanged: theverify_howso_installconsole script andpython -m howso.utilities.installation_verificationresult is NonebranchAll unit tests (old and new pass). Also tested the new functionality on a real Windows Server 2022 and verified functionality (except the one that requires more than 64 cores).