-
Notifications
You must be signed in to change notification settings - Fork 30.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--trace-sync-io regression between v10.10 and v10.11 #28913
Labels
lib / src
Issues and PRs related to general changes in the lib or src directory.
regression
Issues related to regressions.
Comments
ChALkeR
added
the
lib / src
Issues and PRs related to general changes in the lib or src directory.
label
Jul 31, 2019
I will take a closer look |
This is caused by removal of 7fa5f54 breaks the logic behind Revert in progress. Upd: #28926 |
3 tasks
ChALkeR
added a commit
to ChALkeR/io.js
that referenced
this issue
Aug 2, 2019
This reverts commit 7fa5f54. The reverted commit breaks the logic behind --trace-sync-io, it should be enabled only at a certain point in time, while that commit enables it from the very start, causing warnings be printed for all sync io instead of sync io after the first tick of the event loop as documented. Fixes: nodejs#28913 Refs: nodejs#22726 Refs: https://nodejs.org/api/cli.html#cli_trace_sync_io PR-URL: nodejs#28926
BridgeAR
pushed a commit
that referenced
this issue
Aug 6, 2019
This reverts commit 7fa5f54. The reverted commit breaks the logic behind --trace-sync-io, it should be enabled only at a certain point in time, while that commit enables it from the very start, causing warnings be printed for all sync io instead of sync io after the first tick of the event loop as documented. Fixes: #28913 Refs: #22726 Refs: https://nodejs.org/api/cli.html#cli_trace_sync_io PR-URL: #28926 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
addaleax
added a commit
to addaleax/node
that referenced
this issue
Aug 6, 2019
Refactor `test/parallel/test-sync-io-option.js` to be simpler and cover more cases (in particular, this adds a regression test for nodejs#28913). Refs: nodejs#28913
Trott
pushed a commit
to Trott/io.js
that referenced
this issue
Aug 8, 2019
Refactor `test/parallel/test-sync-io-option.js` to be simpler and cover more cases (in particular, this adds a regression test for nodejs#28913). Refs: nodejs#28913 PR-URL: nodejs#29020 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
targos
pushed a commit
that referenced
this issue
Aug 19, 2019
Refactor `test/parallel/test-sync-io-option.js` to be simpler and cover more cases (in particular, this adds a regression test for #28913). Refs: #28913 PR-URL: #29020 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
lib / src
Issues and PRs related to general changes in the lib or src directory.
regression
Issues related to regressions.
Darwin MacBook-ChALkeR.local 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64
lib/src
--trace-sync-io is not expected to produce output before the first tick, and is not expected to print things when the source file does not trigger sync io. Both expectations fail now.
Examples:
Nothing
// Nothing
Expected, v10.10.0: nothing,
.
Obtained (v10.11.0, v12.7.0 is almost equivalent with trace differences):
Click to expand
No output expected
Expected, v10.10: nothing,
.
Obtained (v10.11.0, v12.7.0 is almost equivalent with trace differences):
Click to expand
Note how
statSync
call is also included (it shouldn't be), this is not just the garbage in the front.Some output expected
Expected, v10.10:
Obtained (v10.11.0, v12.7.0 is almost equivalent with trace differences):
Click to expand
Refs: #1707
The text was updated successfully, but these errors were encountered: