Cherry-picked only the test changes from PR969: #972
Closed
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
The total_count_change value should be the incremental changes in total_count since the last time the listener was called or the status was read. Tested and fixed this for on_offered_deadline_missed and on_requested_deadline_missed, see issue OpenDDS#619 * tests/DCPS/Deadline/DataReaderListenerImpl.cpp: * tests/DCPS/Deadline/DataReaderListenerImpl.h: * tests/DCPS/Deadline/DataWriterListenerImpl.cpp: * tests/DCPS/Deadline/DataWriterListenerImpl.h: * tests/DCPS/Deadline/publisher.cpp: * tests/DCPS/Deadline/subscriber.cpp:
|
Why cherry-pick my changes in a new PR? |
Just trying it to see the test results on Jenkins. We won't merge this one. |
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.
The total_count_change value should be the incremental changes in total_count since the last time the listener was called or the status was read. Tested and fixed this for on_offered_deadline_missed and on_requested_deadline_missed, see issue #619