[CI] - disable hab2 multi-proc benchmark assertions #1455
Merged
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.
Motivation and Context
Disabling CI regression assertions on multi-processing hab2 benchmark in light of recently observed flakyness.
Possible source of flakyness is resource limits. CI machine claims to have 8vCPU, we run a 16 process benchmark. This could cause thrashing or resource allocation issues.
This should be re-enabled after investigation and possible corrections to the CI benchmarking workflow.
We'll still run the multi-process benchmark and generate artifacts for debugging and investigation purposes.
How Has This Been Tested
CI shows benchmark regression with habitat-sim commit (facebookresearch/habitat-sim@8eb02ad).
Local testing on cluster shows no regression.
Contents of commit should not impact performance, so CI flakyness is likely.
Types of changes
Checklist