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

Streams: Check constructor and method names #7035

Merged

Conversation

ricea
Copy link
Contributor

@ricea ricea commented Aug 29, 2017

Check the .name properties of constructors and methods for the Streams API.

Also add properties tests for ReadableByteStreamController,
ReadableStreamBYOBReader and ReadableStreamBYOBRequest.

Check the .name properties of constructors and methods for the Streams API.

Also add properties tests for ReadableByteStreamController,
ReadableStreamBYOBReader and ReadableStreamBYOBRequest.
@w3c-bots
Copy link

w3c-bots commented Aug 29, 2017

Build PASSED

Started: 2017-08-29 11:39:35
Finished: 2017-08-29 12:03:56

Failing Jobs

  • chrome:unstable
  • safari:10.0
  • MicrosoftEdge:14.14393

View more information about this build on:

Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

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

Setting aside pre-existing duplication issues, LGTM.

assert_array_equals(Object.getOwnPropertyNames(proto).sort(), properties);

for (const m of methods) {
const propDesc = Object.getOwnPropertyDescriptor(proto, m);
Copy link
Member

Choose a reason for hiding this comment

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

Lots of duplication here and elsewhere, but meh...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I know. I wanted to use the structure I used in writable-streams/properties.js but the need to fetch ReadableStreamBYOBRequest asynchronously meant it wouldn't work directly. So then I just decided to go ahead and land this before the scope creep got any worse.

@ricea
Copy link
Contributor Author

ricea commented Aug 29, 2017

I'm a bit worried that the Travis failures for Safari and Edge might mean the test never completes on those browsers. Does w-p-t have a way of dealing with that if I merge this change?

@domenic
Copy link
Member

domenic commented Aug 29, 2017

My interpretation was that the WPT infra is just broken and not running tests in any browsers. (Since Chrome is not working either.) Let me ask in #testing IRC to see what's up.

@domenic
Copy link
Member

domenic commented Aug 29, 2017

gsnedders helpfully said

Chrome looks like the same old probably-ChromeDriver issue, Safari/Edge look like Sauce being down again

So I think we can merge this.

@domenic domenic merged commit 7a05e4d into web-platform-tests:master Aug 29, 2017
@ricea ricea deleted the streams-check-function-names branch September 1, 2017 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants