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

Hashbang tests update #2065

Merged
merged 8 commits into from
Feb 14, 2019
Merged

Hashbang tests update #2065

merged 8 commits into from
Feb 14, 2019

Conversation

leobalter
Copy link
Member

This replaces #1983 with new changes

@leobalter
Copy link
Member Author

cc @bmeck

bmeck
bmeck previously approved these changes Feb 5, 2019
Copy link
Member

@bmeck bmeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@caitp
Copy link
Contributor

caitp commented Feb 5, 2019

I'd still be happier if parseTestRecord.py supported this upstream, so that running the tests in v8 only requires a tiny change to support.

@leobalter
Copy link
Member Author

I'd still be happier if parseTestRecord.py supported this upstream, so that running the tests in v8 only requires a tiny change to support.

Yes, I'm yet to look at that part. Thanks for the reminder.

@leobalter
Copy link
Member Author

It wasn't easy to find the bug but I finally figure it out. I'm rewriting this python script to something that reflects better the current reality of Test262 tests but providing the same returns not avoid breaking anything else. I'll let you know when it's ready.

]) {
assert.throws(SyntaxError, () => ctor('#!\n_',''), `${ctor.name} Call argument`);
assert.throws(SyntaxError, () => ctor('#!\n_'), `${ctor.name} Call body`);
assert.throws(SyntaxError, () => new ctor('#!\n_',''), `${ctor.name} Construct argument`);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: missing space after comma

GeneratorFunction,
AsyncGeneratorFunction,
]) {
assert.throws(SyntaxError, () => ctor('#!\n_',''), `${ctor.name} Call argument`);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: missing space after comma


assert.sameValue(eval('#!\n'), undefined);
assert.sameValue(eval('#!\n1'), 1)
assert.sameValue(eval('#!2\n'), undefined);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let’s try both direct and indirect eval.

@mathiasbynens
Copy link
Member

re: file names like encoded-bang-041.js, I’d prefer escaped over encoded to match the phrasing used in the spec for escape sequences

LGTM % comments

mathiasbynens
mathiasbynens previously approved these changes Feb 7, 2019
- indirect eval
- files renaming
- space after comma
@leobalter leobalter dismissed stale reviews from mathiasbynens and bmeck via 0084c7c February 8, 2019 16:06
@leobalter
Copy link
Member Author

@mathiasbynens I applied the feedback there.

Still working on the python script.

@rwaldron rwaldron merged commit 6e4b434 into master Feb 14, 2019
@leobalter leobalter deleted the hashbang branch February 19, 2019 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants