Skip to content

validate: add action to check pipeline latency

First shot of implementing latency checking, see #5 (moved)

This is the easiest way. I'm wondering if it wouldn't be best to have something more declarative, like say in the scenario "the pipeline latency should never exceed $n" and then have validate automatically checking it each time the latency is updated (GST_MESSAGE_LATENCY).

@thiblahute : what do you think? Do we have such semantics in validate scenarios at the moment?

Edited by Guillaume Desmottes

Merge request reports

Loading