Incorrectly indented code resulted in only reporting an error when a failure occurred on the highest sample rate; failures at lower sample rates were silently ignored. All the instances recorded on the confluence page tracking failures for issue 134 occur at the highest sample rate for the config being tested.
I think we can now expect failures to occur more often and at all sample rates, matching the expectation from the glitches in analogue input testing.
Incorrectly indented code resulted in only reporting an error when a failure occurred on the highest sample rate; failures at lower sample rates were silently ignored. All the instances recorded on the confluence page tracking failures for issue 134 occur at the highest sample rate for the config being tested.
I think we can now expect failures to occur more often and at all sample rates, matching the expectation from the glitches in analogue input testing.