Figure out how to deal with test262 tests that don't play well with an inherited shell.js
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
People
(Reporter: Waldo, Unassigned)
References
(Blocks 1 open bug)
Details
The next test262 update is going to add test262/built-ins/AsyncFunction/is-not-a-global.js. Simple test, just verifies there's no global AsyncFunction binding.
But: test262/built-ins/AsyncFunction/is-a-constructor.js in the same directory has includes: [isConstructor.js, hidden-constructors.js]. And that results in that directory's generated shell.js including the latter script, which does define a global var AsyncFunction.
These two tests do not play well with file system-inherited shell.js. We could "fix" upstream as a hackaround, but this issue is probably going to manifest more than just this once. Or we could inline includes into imported test files -- but only if includes are not supposed to be processed as separate Script productions, not sure if they are. Or maybe something else.
But for now, I'm just going to disable this test so I can finish updating test262. We would pass the test if we ran it correctly, so this is only an import-script bug, not a bug in our engine.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•1 year ago
|
Description
•