Skip to content
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

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

Merged
merged 1 commit into from
May 11, 2016

Conversation

MylesBorins
Copy link
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

@MylesBorins MylesBorins 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
Member

jasnell commented Apr 20, 2016

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
Contributor Author

@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
Member

jasnell commented Apr 20, 2016

this would need to be rebased now ;-)

@MylesBorins
Copy link
Contributor Author

@jasnell rebased

@bnoordhuis
Copy link
Member

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

@indutny
Copy link
Member

indutny commented Apr 28, 2016

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

@MylesBorins MylesBorins force-pushed the fix-vm-cached-data branch 2 times, most recently from e70f2cc to 43166c0 Compare May 9, 2016 20:34
@MylesBorins
Copy link
Contributor Author

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

PTAL and let me know if this is ok

@indutny
Copy link
Member

indutny commented May 9, 2016

LGTM

2 similar comments
@bnoordhuis
Copy link
Member

LGTM

@targos
Copy link
Member

targos commented May 10, 2016

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 <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
@MylesBorins MylesBorins merged commit 9460b20 into nodejs:master May 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 <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Issues and PRs related to the tests. vm Issues and PRs related to the vm subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants