Adding wait for file ready condition - #500
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
44a90d5 to
eef82f2
Compare
eef82f2 to
23e104b
Compare
23e104b to
49175a2
Compare
49175a2 to
a3a0e33
Compare
a3a0e33 to
91e1f5e
Compare
| @@ -0,0 +1,53 @@ | |||
| /******************************************************************************** | |||
There was a problem hiding this comment.
Should this file be called control_client_test_driver like for the other integration tests?
There was a problem hiding this comment.
I've rename however we should decide on a central one, in the script
it's fake it seems.5ba0c35 to
6883f7b
Compare
| virtual ~IFileWaiter() = default; | ||
|
|
||
| /// @see wait_for_file() for more info. | ||
| virtual OsalReturnType waitForFile( |
There was a problem hiding this comment.
does it make sense to split this into two methods:
waitForFileExistence
waitForFileRemoval
?
The list of arguments is getting quite long.
I wonder if it would make sense to configure the poll_interval in the constructor?
There was a problem hiding this comment.
I don't think so, the implementation is 90% the same, and the difference between waiting for existence or deletion is only one if, which I think is easy enough to read so don't think making a separate private method makes sense either
if (!wait_for_existence)
{
return OsalReturnType::kSuccess;
}
Adding wait for file functionality.