Uh oh!
There was an error while loading. Please reload this page.
src: add sync trace to fs - #19649
Conversation
Trott
commented
Mar 28, 2018
@nodejs/fs |
There was a problem hiding this comment.
Maybe pass this as a parameter to SyncCall and call FS_SYNC_TRACE_BEGIN and FS_SYNC_TRACE_END from there?
There was a problem hiding this comment.
Thanks very much for the comment. I also considered adding trace begin and end into SyncCall. These trace functions are flexible to take additional useful tracing data whenever making sense such as number of bytes read for read(). Since SyncCall is already a variadic function, it will be a little messy to introduce arbitrary trace arguments there. It seems cleaner to leave SyncCall API unchanged and call trace begin and end variadic functions separately.
There was a problem hiding this comment.
@chinhuang007 Good point, I missed the call below that passes additional arguments to the macros, sorry about that.
9ab8e6a to
f77f35eComparejoyeecheung
commented
Mar 29, 2018
f77f35e to
79d3738Comparechinhuang007
commented
Mar 30, 2018
I fixed the conflicts in src/node_file.cc. Can someone start a new CI please? |
79d3738 to
a8fd0fcCompareyhwang
commented
Apr 2, 2018
08bccce to
812a9c7Compareyhwang
commented
Apr 2, 2018
Another new CI to help the problem investigation: https://ci.nodejs.org/job/node-test-commit/17366/ |
a963af0 to
4f5d1feComparechinhuang007
commented
Apr 3, 2018
Thanks. Most CI issues were fixed by avoid using relative paths. Also found and fixed the AIX issues. Please start a new CI. |
yhwang
commented
Apr 3, 2018
029097a to
1bd5f51CompareThere was a problem hiding this comment.
I'd prefer to not have to define these as static strings this way and just build it in to the macro such that, for instance, FS_SYNC_TRACE_BEGIN(access) would expand out to fs.access
8a8c31d to
b266ed0Comparechinhuang007
commented
Apr 3, 2018
I merged with upstream, fixed the lint issue, and changed to use macros instead of static strings as @jasnell commented. Can someone start a CI? |
joyeecheung
commented
Apr 4, 2018
There was a problem hiding this comment.
To group this better with other trace event test cases, please use a file name like test-trace-events-fs-sync.js
chinhuang007
commented
Apr 9, 2018
@joyeecheung Thanks for the heads-up. I just rebased my master and this branch and passed local tests. Can someone start an CI to see if everything is good? |
yhwang
commented
Apr 9, 2018
chinhuang007
commented
Apr 9, 2018
CI passed all tests except on linux-linked-debug, failing on test-http-readable-data-event, and on arm-fanned, failing on Waiting for next available executor on pi1-docker. Both seem unrelated to this PR. |
mhdawson
commented
Apr 12, 2018
New CI since we are trying to have green CI before landing: https://ci.nodejs.org/job/node-test-pull-request/14233/ |
jasnell
commented
Apr 14, 2018
CI failures appear unrelated. |
Add sync trace to fs operations which is enabled by the node.fs.sync trace event category. Also add a general test js file to verify all operations. PR-URL: #19649 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
jasnell
commented
Apr 14, 2018
Landed in 09c6346 |
Add sync trace to fs operations which is enabled by the node.fs.sync trace event category. Also add a general test js file to verify all operations. PR-URL: #19649 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Add the trace category for file system synchronous methods to documentation so the users can enable it when they want to look into file system sync method trace data. Refs: nodejs#19649
Add the trace category for file system synchronous methods to documentation so the users can enable it when they want to look into file system sync method trace data. PR-URL: #20526 Refs: #19649 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Add the trace category for file system synchronous methods to documentation so the users can enable it when they want to look into file system sync method trace data. PR-URL: #20526 Refs: #19649 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Add the trace category for file system synchronous methods to documentation so the users can enable it when they want to look into file system sync method trace data. PR-URL: #20526 Refs: #19649 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Add the trace category for file system synchronous methods to documentation so the users can enable it when they want to look into file system sync method trace data. PR-URL: #20526 Refs: #19649 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Add sync trace to fs operations which
is enabled by the node.fs.sync trace event
category. Also add a general test js file
to verify all operations.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes