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
Using .withInfiniteTimout() sets the timeout value to -1.
In the until method of InteractBuilderImpl we then have the following:
final long time = System.currentTimeMillis();
...
if (System.currentTimeMillis() - time > expect.getTimeout()) {
LOG.fine("Until matching operation timeout");
return (R) SimpleResult.failure(inputBuffer, true);
}
Since getTimeout() will evaluate to -1, this will enter the if statement and return as a failure.
So any interact statement I built using an expect with infinite timeout will not function, and will simply exit without even evaluating the matchers.
Setting the timeout to something huge (e.g. 10 days) is a work-around.
The text was updated successfully, but these errors were encountered:
Using .withInfiniteTimout() sets the timeout value to -1.
In the until method of InteractBuilderImpl we then have the following:
Since getTimeout() will evaluate to -1, this will enter the if statement and return as a failure.
So any interact statement I built using an expect with infinite timeout will not function, and will simply exit without even evaluating the matchers.
Setting the timeout to something huge (e.g. 10 days) is a work-around.
The text was updated successfully, but these errors were encountered: