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.
Follow-up to #345
IIRC only on the MacOS Java CI jobs we could observe that the
next()
method was triggered unreliably (usually this should be called every second). As a result the check whether a Heartbeat should be sent was sometimes called too late. This lead to failures in theTimerTest
.I decided to get rid of the
TimerTest
since in the wild this unreliable triggering of heartbeats would be not a big problem and especially the heartbeat interval of 2 seconds that the test used was ridiculously low. So for a normal heartbeat interval of 30 seconds there is no problem when the heartbeat is generated say 100ms too late.TimerTest
was replaced by a simple unit test with a few lines:quickfixj/quickfixj-core/src/test/java/quickfix/SessionStateTest.java
Lines 73 to 88 in 19fd341