gstreamer/validate/data/scenarios/change_state_intensive.scenario

description, duration=0, summary="Set state to NULL->PLAYING->NULL 20 times", need-clock-sync=true, min-media-duration=1.0, live_content_compatible=True, handles-states=true, ignore-eos=true
set-state, state="playing", sub-action="set-state, state=null", repeat=40
stop;
validate:scenario: Add a way to ignore EOS And ignore then in seek_forward/backward to avoid cases where the pipeline EOS before we have the chance to launch the following seek, see: https://ci.gstreamer.net/job/GStreamer-master-meson-validate/3483/testReport/junit/(root)/gst-validate-launcher/validate_rtsp_playback_seek_backward_raw_h264_1_mp4/ 2019-03-16 21:05:56 +00:00			`description, duration=0, summary="Set state to NULL->PLAYING->NULL 20 times", need-clock-sync=true, min-media-duration=1.0, live_content_compatible=True, handles-states=true, ignore-eos=true`
validate: Fix the change_state_intensive scenario The scenario was in no way certified that the pipeline was in PAUSED state when starting on an stream that does not preroll 2017-06-22 15:53:49 +00:00			`set-state, state="playing", sub-action="set-state, state=null", repeat=40`
validate: Add a scenario that switches state many intensively + Use it by default in the launcher tests 2014-05-07 11:14:51 +00:00			`stop;`