Summary

drivers_orchestration uses `time.sleep(attempt * 1000)` to sleep between attempts, but `time.sleep` expects seconds, so we're sleeping way too long.

Motivation

Who is the affected end user?

Drivers developers.

How does this affect the end user?

None.

How likely is it that this problem or use case will occur?

Main path for orchestration.

If the problem does occur, what are the consequences and how severe are they?

Very slow orchestration.

Is this issue urgent?

No, this has been the case for a while now.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Test improvements.

Acceptance Criteria

Orchestration does not sleep 1000s of seconds between retries.