vyommani commented on PR #667:
URL: https://github.com/apache/ranger/pull/667#issuecomment-3454391822
> @vyommani I see the usages of `timeout/sleep` in the tests so asking, how
much time latency does the new tests add to the current tests? Would it be a
good idea to keep constants like `TEST_TIMEOUT_SECONDS` in a constants class
whereby all timeouts across different tests can be maintained in a single file,
it might be helpful to segment these variables for (short, mod, long) running
tests.
>
> CC: @mneethiraj
@kumaab, It will be really good if we create a separate file where we put
all the wait timeout etc. For the newly added test below are the approximate
worst and average case times.
Worst-case latency: 10-15 seconds (due to factors like slow I/O, thread
scheduling, or retries)
Actual latency:
1->Latch countdown: 100-500 ms
2->File polling: under 1 second
3->Real average per test: ~1-3 seconds
The latency is deemed acceptable to ensure reliable testing of the
PolicyRefresher background thread, which involves:
Asynchronous policy loading
1->Polling Ranger Admin
2->Writing cached policies to disk
3->Handling retries and edge cases
Without these waits, tests might be flaky, passing locally but failing in CI
due to timing issues.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
