-
Notifications
You must be signed in to change notification settings - Fork 4
Test MAP Message Count Progression
A series of processed MAP Messages. In the first half, the msgIssueRevision field increments exactly as it should each time, while the Revision field's changes are exercised. After 8 messages comes a 6-second pause, then the process repeats as it exercises msgIssueRevision changes while Revision increments according to specifications.
- A baseline MAP.
- 1 second later, a changed MAP with an incremented message count.
- 500 ms later, a changed MAP with the same message count. This generates an event, because the change should have led to a message count increment.
- 500 ms later, a changed MAP with a message count increased by 10. This generates an event, because the message count should have only increased by 1.
- 500 ms later, a changed MAP with an incremented message count.
- 500 ms later, a changed MAP with an incremented message count that wraps around from 127 to 0. This does not generate an event.
- 6 seconds later, a changed MAP with a message count increased by 10. This does not generate an event, because the different message appears outside the maximum time window of 5 seconds.
- 500 ms later, a changed MAP with an incremented message count.
topic.CmMapMessageCountProgressionEvents
Four MapMessageCountProgressionEvents produced on the topic within 30 seconds; the first 2 are caused by inconsistencies with the Revision field while the second two are caused by inconsistencies with the MsgIssueRevision field.
Topic: topic.CmMapMessageCountProgressionEvents
% Waiting for group rebalance
% Group group rebalanced (memberid rdkafka-11d3cfe7-06cc-4d90-acc4-f73ea8b5b6cb): assigned: topic.CmMapRevisionCounterEvents [0]
% Reached end of topic topic.CmMapRevisionCounterEvents [0] at offset 0
{"eventGeneratedAt":1731693158052,"eventType":"MapMessageCountProgression","intersectionID":0,"roadRegulatorID":0,"messageType":"MAP","messageCountA":116,"timestampA":"2024-11-15T17:52:36.526Z[UTC]","messageCountB":116,"timestampB":"2024-11-15T17:52:37.026Z[UTC]"}
% Reached end of topic topic.CmMapMessageCountProgressionEvents [0] at offset 1
{"eventGeneratedAt":1731693174047,"eventType":"MapMessageCountProgression","intersectionID":0,"roadRegulatorID":0,"messageType":"MAP","messageCountA":116,"timestampA":"2024-11-15T17:52:52.526Z[UTC]","messageCountB":116,"timestampB":"2024-11-15T17:52:53.026Z[UTC]"}
% Reached end of topic topic.CmMapMessageCountProgressionEvents [0] at offset 2
{"eventGeneratedAt":1731693192344,"eventType":"MapMessageCountProgression","intersectionID":0,"roadRegulatorID":0,"messageType":"MAP","messageCountA":116,"timestampA":"2024-11-15T17:53:10.811Z[UTC]","messageCountB":116,"timestampB":"2024-11-15T17:53:11.311Z[UTC]"}
% Reached end of topic topic.CmMapMessageCountProgressionEvents [0] at offset 3
{"eventGeneratedAt":1731693192835,"eventType":"MapMessageCountProgression","intersectionID":0,"roadRegulatorID":0,"messageType":"MAP","messageCountA":116,"timestampA":"2024-11-15T17:53:11.311Z[UTC]","messageCountB":126,"timestampB":"2024-11-15T17:53:11.811Z[UTC]"}
% Reached end of topic topic.CmMapMessageCountProgressionEvents [0] at offset 4
If the MAP messages for this intersection has been sent prior to this test, the result may differ from the above. Re-running the script within 5 seconds of finishing the previous run may trigger an additional event as the message count jumps from 7 to 115 within the time window.