| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The test has two test cases, but only the first was being run due to a small bug. This change fixes the bug.
There was a problem hiding this comment.
Good catch, and my apologies again. This test is definitely not written in a way that makes it easy to reason about it.
These changes look good to me. Eventually it would be good to also assert on the number of blockingCallback calls, but that can be done in a separate PR. This is already a significant improvement.
Sorry, something went wrong.
|
|
||
| timeCallbackScheduled = Timer.now(); | ||
| setTimeout(blockingCallback, TIMEOUT); | ||
| setTimeout(blockingCallback.bind(null, callback), TIMEOUT); |
There was a problem hiding this comment.
setTimeout(() => blockingCallback(callback), TIMEOUT); ?
Sorry, something went wrong.
There was a problem hiding this comment.
I did it this way to match what was already on line 67 so that it was clear that they were doing the same thing.
Sorry, something went wrong.
Sorry, something went wrong.
The test has two test cases, but only the first was being run due to a small bug. This change fixes the bug. PR-URL: nodejs#9305 Reviewed-By: Julien Gilli <jgilli@nodejs.org> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
The test has two test cases, but only the first was being run due to a small bug. This change fixes the bug. PR-URL: #9305 Reviewed-By: Julien Gilli <jgilli@nodejs.org> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
The test has two test cases, but only the first was being run due to a small bug. This change fixes the bug. PR-URL: #9305 Reviewed-By: Julien Gilli <jgilli@nodejs.org> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
test timers
Description of change
The test has two test cases, but only the first was being run due to a
small bug. This change fixes the bug.
/cc @misterdjules
Refs: #8041