Skip to content

test: fix test-vm-cached-data to work with old v8 - #6317

Merged
MylesBorins merged 1 commit into
nodejs:masterfrom
MylesBorins:fix-vm-cached-data
May 11, 2016
Merged

test: fix test-vm-cached-data to work with old v8#6317
MylesBorins merged 1 commit into
nodejs:masterfrom
MylesBorins:fix-vm-cached-data

Conversation

@MylesBorins

Copy link
Copy Markdown
Contributor

while let no longer needs to run in strict mode in v8 5.x it throws
in v8 4. This modification will make the test-vm-cached-data work in
older version of node.

I am under the impression that these changes were made to test features that will only be available in v8 5. So perhaps we don't care to support older versions. Either way it might be nice to be explicit with the code being shelled out.

I've currently marked #6280 as dont-land-on-v5.x, but we can change that if this lands

/cc @jasnell@indutny

@MylesBorinsMylesBorins added vm Issues and PRs related to the vm subsystem. test Issues and PRs related to the tests. labels Apr 20, 2016
@jasnell

Copy link
Copy Markdown
Member

hmm... not sure there's enough value at this point with v6 right around the corner. If we were going to pull this back to v4 then I think I'd be +1 for sure.

@MylesBorins

Copy link
Copy Markdown
ContributorAuthor

@jasnell I figured we would probably not want it... but had already made the patch and it was small enough I figured we might want to be explicit

@jasnell

Copy link
Copy Markdown
Member

this would need to be rebased now ;-)

@estliberitas
estliberitasforce-pushed the master branch 2 times, most recently from 7da4fd4 to c7066fbCompareApril 26, 2016 05:23
@MylesBorins

Copy link
Copy Markdown
ContributorAuthor

@jasnell rebased

@bnoordhuis

Copy link
Copy Markdown
Member

LGTM but can you capitalize 'while' and use 'Refs:' in the commit log?

@indutny

Copy link
Copy Markdown
Member

LGTM, but may be we should just turn the only let here to var instead?

@MylesBorins
MylesBorinsforce-pushed the fix-vm-cached-data branch 2 times, most recently from e70f2cc to 43166c0CompareMay 9, 2016 20:34
@MylesBorins

Copy link
Copy Markdown
ContributorAuthor

I've updated with both of your suggestions @bnoordhuis / @indutny

PTAL and let me know if this is ok

@indutny

Copy link
Copy Markdown
Member

LGTM

2 similar comments
@bnoordhuis

Copy link
Copy Markdown
Member

LGTM

@targos

Copy link
Copy Markdown
Member

LGTM

While `let` no longer needs to run in `strict mode` in v8 5.x it throws
in v8 4. This modification will make the test-vm-cached-data work in
older version of node.
Refs: nodejs#6280
PR-URL: nodejs#6317
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
@MylesBorins
MylesBorins merged commit 9460b20 into nodejs:masterMay 11, 2016
@MylesBorins
MylesBorins deleted the fix-vm-cached-data branch May 12, 2016 18:14
evanlucas pushed a commit that referenced this pull request May 17, 2016
While `let` no longer needs to run in `strict mode` in v8 5.x it throws
in v8 4. This modification will make the test-vm-cached-data work in
older version of node.
Refs: #6280
PR-URL: #6317
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testIssues and PRs related to the tests.vmIssues and PRs related to the vm subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@MylesBorins@jasnell@bnoordhuis@indutny@targos