Skip to content

Commit

Permalink
Fix false positive in basic telemetry test
Browse files Browse the repository at this point in the history
It's possible (especially with ROAST_TIMING_SCALE) that Telemetry takes
multiple snapshots while we give it time to do at least one. So adjust the
test to expect at least one snapshot to be taken, but be fine with moar than
one. This fits the test description of "did the snapper start taking snaps"
  • Loading branch information
niner committed Aug 25, 2021
1 parent 9681a09 commit c0a6823
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion t/06-telemetry/01-basic.t
Expand Up @@ -78,7 +78,7 @@ ok +periods() == 0, 'did the snapper actually stop';

snapper(2);
sleep .5 * (%*ENV<ROAST_TIMING_SCALE>//1); # give snapper thread some time to start up
is +periods(), 1, 'did the snapper start taking snaps';
ok +periods() >= 1, 'did the snapper start taking snaps';
snapper(:stop);
sleep 2 * (%*ENV<ROAST_TIMING_SCALE>//1);

Expand Down

0 comments on commit c0a6823

Please sign in to comment.