Conversation
|
Even though we're TurboFan by default now, I would still be cautious about permanent deopts when using |
|
@mscdex I did that and there was no new constant deopt. |
|
Actually I just checked current master and it looks like Typically you will see a lot of output with that command I gave, because tests tend to have a lot of deopts (although the EDIT: It looks like I was mistaken. I'm guessing I just haven't ran that since the switch to V8 5.9 and TurboFan by default. There's only about 6 perm deopts as of this writing and I believe they're all inside the tests themselves. |
Yes, but we also have the |
|
@gibfahn We had |
test/common/index.js
Outdated
There was a problem hiding this comment.
It seems this line can be removed now.
cjihrig
left a comment
There was a problem hiding this comment.
LGTM with @vsemozhetbyt's comment addressed.
|
While the code changes look good, I'd much rather the changes to each of the separate tools be in their own separate commits. On the off chance that we need to revert any particular item, it would make it significantly easier. |
@BridgeAR If I understand @jasnell correctly separate commits not PRs (not like we did for |
|
Comments addressed. I'm not to sure about the commit messages though. |
Personally I would do |
|
Maybe even |
tools/license2rtf.js
Outdated
There was a problem hiding this comment.
Suggestion
const {li, in_license_block: lic} = paragraph;
tools/license2rtf.js
Outdated
There was a problem hiding this comment.
const line_indent = Math.floor(line_strip_length / 2) * 2;
There was a problem hiding this comment.
suggestion:
module.exports = function({report, options:requiredModules})
|
About my suggestions, if we're churning, let's make some butter (or code better). |
|
PTAL I'd rebase and address the comments after getting some more feedback. |
|
Rebased and comments addressed |
|
pre-land CI: https://ci.nodejs.org/job/node-test-commit/10891/ |
There was a problem hiding this comment.
something here fails the linter:
Running JS linter...
./node tools/jslint.js -j 2 -f tap -o test-eslint.tap \
benchmark doc lib test tools
/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/rule-context.js:210
this.eslint.report(
^
TypeError: Cannot read property 'eslint' of undefined
at report (/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/rule-context.js:210:13)
at /usr/home/iojs/build/workspace/node-test-linter/tools/eslint-rules/required-modules.js:79:11
at Array.forEach (native)
at Linter.Program:exit (/usr/home/iojs/build/workspace/node-test-linter/tools/eslint-rules/required-modules.js:78:24)
at emitOne (events.js:101:20)
at Linter.emit (events.js:188:7)
at NodeEventGenerator.applySelector (/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/util/node-event-generator.js:265:26)
at NodeEventGenerator.applySelectors (/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/util/node-event-generator.js:294:22)
at NodeEventGenerator.leaveNode (/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/util/node-event-generator.js:317:14)
at CodePathAnalyzer.leaveNode (/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/code-path-analysis/code-path-analyzer.js:622:23)
at Traverser.leave (/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/linter.js:925:36)
gmake: *** [Makefile:876: jslint-ci] Error 2
/usr/home/iojs/build/workspace/node-test-linter/tools/eslint/lib/rule-context.js:210
this.eslint.report(
^PR-URL: nodejs#13732 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#13732 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#13732 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#13732 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#13732 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#13732 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
PR-URL: nodejs#13732 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com>
|
@nodejs/build this PR touches some of the tools that are not covered by the tests, anyway to verify they work as expected also where the are needed? |
|
@refack If I'm not missing anything, this only influences |
Thanks! |
As far as I know using const is preferable in almost all situations, so this converts probably all
vardeclarations toconst, if possible.If this is not what you want, I'm happy to close this again or split into smaller parts.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
tools,test