Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Liveliness Qos Updates - Fix failing test observed in some cases. #403

Merged
merged 1 commit into from
Jan 17, 2017

Conversation

oschwaldp-oci
Copy link
Contributor

Update requirements for expected values. Base pass/fail on alive_count instead of trying to track all variables in the liveliness update. This is due to two possible states after receiving the SYSTEM_SHUTDOWN message. Not alive count could go to 1 or straight to 0 based on how the writer shuts down but does not alter the actual test pass/fail requirements. (In a test-passing scenario the AlertDataReaderListenerImpl could receive either 2 or 3 liveliness updates depending on timing).

…t instead of trying to track all variables in the liveliness update. This is due to two possible states after receiving the SYSTEM_SHUTDOWN message. Not alive count could go to 1 or straight to 0 based on how the writer shuts down but does not alter the actual test pass/fail requirements. (In a test-passing scenario the AlertDataReaderListenerImpl could receive either 2 or 3 liveliness updates depending on timing).
@mitza-oci mitza-oci merged commit 5da3f44 into OpenDDS:master Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants