You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test remembers start_timestamp, then receives all frames and remembers end_timestamp like this:
# read stop condition > real time delta from job config
realtime_delta = job_config.get("stop_condition", {}).get("real_time_delta_ms", {}).get("configured_delta_ms", 0) * 1000000
if not realtime_delta:
pytest.skip("Job stop condition is expected to be a realtime delta")
end_timestamp = 0
sink_runner = (SinkBuilder()
.with_socket('router+bind:tcp://0.0.0.0:6666')
.with_idle_timeout(30)
.build()
)
start_timestamp = time.monotonic_ns()
for result in sink_runner:
end_timestamp = time.monotonic_ns()
job_status = rest_api.get_job_status(replay_job)
job_lifetime = end_timestamp - start_timestamp
There is no way that end_timestamp is affected by sink timeout since we take the last timestamp from within the loop.
The difference (end_timestamp - start_timestamp) is about 5 seconds, so the test fails:
@aletharel, I do not think the test is correct because you created the job earlier than the sink was created. It starts waiting and retrying, thus you can get a prolonged execution.
There is a test that checks job stop condition by real time delta.
Here is the config fragment with realtime delta set to 30 seconds:
The test remembers start_timestamp, then receives all frames and remembers end_timestamp like this:
There is no way that end_timestamp is affected by sink timeout since we take the last timestamp from within the loop.
The difference (end_timestamp - start_timestamp) is about 5 seconds, so the test fails:
I am not sure if this is a bug or just an admissible error.
The text was updated successfully, but these errors were encountered: