Fix the ActivateWithWrongJointsNamesFails test#1570
Merged
Conversation
Member
Author
|
@Mergifyio backport mergify/bp/humble/pr-1568 |
Contributor
✅ Backports have been createdDetails
|
saikishor
previously approved these changes
Mar 4, 2025
Member
|
@christophfroehlich thanks for taking care of the fix |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1570 +/- ##
==========================================
- Coverage 84.78% 84.75% -0.03%
==========================================
Files 124 124
Lines 11439 11441 +2
Branches 963 965 +2
==========================================
- Hits 9698 9697 -1
+ Misses 1433 1432 -1
- Partials 308 312 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
It came up with the fix introduced with #1568