Skip to content

Tdma Scripted burns first slot to assure test order as laid out in test plan. CI test uses ~transmit topic rather than tdma status for testing

Caileigh Fitzgerald requested to merge issue/40-bug-in-tdma_scripted-node-uses-params-from-launch-rate-max_bytes-for-first-transmit-then into dev/tdma_extended_ci

Issue: #40 (closed)

Bug fix to tdma_scripted:

  • tdma scripted will burn it's very first active slot IF there is an active test plan. This assures the rates/buffer sizes are cycled according to the test plan from the very first packet in the slot.
  • tdma sets the parameters for the first transmit from the test plan rather than using values passed in launch for first TX
  • when the test plan is toggled on from an off state (or it's re-read while running via dynamic reconf) the next active slot will be burned (in case the user toggled during an active slot. This keeps the code simple for handling this case and we won't activate a test plan mid slot)

TODO: better handling for the runtime case. We can probably check and see if we're not active and have a second to load the test plan then we don't burn our first slot. For now it makes the most sense to keep the behavior consistent.

Edited by Caileigh Fitzgerald

Merge request reports