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
I've noticed an intermittent time-based test failure, which probably indicates something is getting the "now" time by default assignment instead of being explicitly assigned in the tests. Something to look into:
Scheduler › getNextRequestDelay › returns the same number when a new request that is scheduled later is added
expect(received).toBe(expected) // Object.is equality
Expected: 119964
Received: 119963
261 | const delayAfter = scheduler.getNextRequestDelay( now );
262 |
> 263 | expect( delayAfter ).toBe( delayBefore );
| ^
264 | } );
265 | } );
266 |
at Object.toBe (src/client/__tests__/scheduler.spec.js:263:25)
The text was updated successfully, but these errors were encountered:
I've noticed an intermittent time-based test failure, which probably indicates something is getting the "now" time by default assignment instead of being explicitly assigned in the tests. Something to look into:
The text was updated successfully, but these errors were encountered: