Open msujew opened 1 month ago
In some of our CI runs (see here), the workspace lock test fails due to minor timing issues in the runtime. This change makes the test a bit more lenient regarding minor inaccuracies in the setTimeout mechanism.
setTimeout
While working on something else, I just faced this issue, where I got the "magical number 9":
9
Therefore, approved from my side 🙂
In some of our CI runs (see here), the workspace lock test fails due to minor timing issues in the runtime. This change makes the test a bit more lenient regarding minor inaccuracies in the
setTimeout
mechanism.