Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.2k
test: add known_issues test for #6287#10272
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
AnnaMag commented Dec 14, 2016 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
fhinkel commented Dec 16, 2016
Is this test "moved" or newly added? |
AnnaMag commented Dec 16, 2016
added- comment fixed. thanks! |
| const assert = require('assert'); | ||
| const vm = require('vm'); | ||
| var context = vm.createContext(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be const?
| const res = vm.runInContext(` | ||
| this.x = 'prop' | ||
| delete this.x; | ||
| Object.getOwnPropertyDescriptor(this, "x"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use single quotes with x here?
| @@ -0,0 +1,15 @@ | |||
| 'use strict' | |||
| // Refs:https://github.com/nodejs/node/issues/6287 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Space after the colon please.
Deleting property in the vm context has no effect as reported in nodejs#6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes.
6dc6f09 to 8667063CompareAnnaMag commented Dec 16, 2016
@cjihrig, done |
Fishrock123 left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
italoacasas commented Dec 18, 2016
Deleting property in the vm context has no effect as reported in #6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes. PR-URL: #10272 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Deleting property in the vm context has no effect as reported in nodejs#6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes. PR-URL: nodejs#10272 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Deleting property in the vm context has no effect as reported in #6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes. PR-URL: #10272 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Deleting property in the vm context has no effect as reported in #6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes. PR-URL: #10272 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Deleting property in the vm context has no effect as reported in #6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes. PR-URL: #10272 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Deleting property in the vm context has no effect as reported in #6287 The test is moved to the known_issues and will be fixed with the 5.5 V8 API changes. PR-URL: #10272 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Checklist
make -j4 test(UNIX), orvcbuild test nosign(Windows) passesAffected core subsystem(s)
tests
Description of change
A test addressing #6287:
Deleting property in the vm context has no effectis added to the known_issues directory.
It will be fixed with the 5.5 V8 API changes