| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
s/Thows/Throws/ ?
Sorry, something went wrong.
There was a problem hiding this comment.
Doesn't this delete the file? How about using another method that calls makeCallback() like, I don't know, fs.chmod()?
The comment should also be updated.
Sorry, something went wrong.
There was a problem hiding this comment.
Good point...but any of the operations which are calling makeCallback have an impact on the file. I would then use fs.mkdtemp which only creates a temp dir which we can delete at the end of the test. Does it make sense to you @lpinca?
Sorry, something went wrong.
There was a problem hiding this comment.
Yes works for me.
Sorry, something went wrong.
There was a problem hiding this comment.
s/Thows/Throws/ ?
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. One suggestion tho: the process.once('warning', ...) bit can be replaced by a call to common.expectWarning(...)
Sorry, something went wrong.
There was a problem hiding this comment.
Can you remove this.
Sorry, something went wrong.
There was a problem hiding this comment.
Should this be os.tmpdir()? Alternatively, there is common.tmpDir for use in tests.
Sorry, something went wrong.
There was a problem hiding this comment.
This throws an error if the test is run in isolation node test/parallel/test-fs-make-callback.js and common.tmpDir has not been created.
I think it makes sense to run common.refreshTmpDir() at the beginning of the test.
Sorry, something went wrong.
There was a problem hiding this comment.
I'd use common.expectWarning() for consistency.
Sorry, something went wrong.
makeCallback and makeStatsCallback are both tested intedependently. Fixes: nodejs#12136
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
CI is green landing |
Sorry, something went wrong.
|
Should this be backported to v6.x-staging? If yes please follow the guide and raise a backport PR, if no let me know or add the dont-land-on label. |
Sorry, something went wrong.
makeCallback and makeStatsCallback are both tested intedependently. PR-URL: #12140 Backport-PR-URL: #13785 Fixes: #12136 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
makeCallback and makeStatsCallback are both tested intedependently. PR-URL: #12140 Backport-PR-URL: #13785 Fixes: #12136 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
makeCallback and makeStatsCallback are both tested intedependently. PR-URL: #12140 Backport-PR-URL: #13785 Fixes: #12136 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
makeCallback and makeStatsCallback are both tested intedependently. PR-URL: nodejs/node#12140 Fixes: nodejs/node#12136 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
| Back | FazBrowse Home | New Git URL |
makeCallback and makeStatsCallback are both tested intedependently.
Fixes: #12136
Checklist
Affected core subsystem(s)
test, fs