Add expectations about auto-inertial warnings #1520
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
Signed-off-by: Steve Peters <scpeters@openrobotics.org>
9 tasks
iche033
approved these changes
Dec 20, 2024
# 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.
Targeting #1513.
This updates expectations for three test cases related to auto-inertial warnings by using the
ERRenforcement policy inParserConfig:ERRand expect a warning about unset collision density. Keep the subsequent parsing with default enforcement policy that expects no errors but will print the warning to the console.ERRand expect a warning about user-specified inertial values. Again keep the subsequent parsing with default enforcement policy that expects no errors but will print the warning to the console.//inertial/poseand//inertial/inertiavalues, parse with enforcement policyERRand expect no warnings/errors.