Re: New webrtc-pc Editor's draft (v20161219)

I believe this is a Respec change, since now any new commit I create now on
master is failing, while the ones I pushed for the release on the 19th, as
well as PRs 974 and 976, were fine.

There was a respec release (7.1.0) on the 20th, but it's not obvious to me
why that one could have resulted in these failures.

I have added Dom to this thread in the hope that he can help figure out
what happened.

-- dan

On Thu, Dec 22, 2016 at 8:45 AM, Daniel Burnett <danielcburnett@gmail.com>
wrote:

> Actually, 'make update' fails on my local machine anyway (see below).  I
> don't usually have success running respec locally, so I typically just
> check the Travis status on GitHub.  I'm not sure why all of our definitions
> are suddenly missing, but I'll look at it and see if I can figure out what
> happened since our last PR was applied before publication.
>
> ---------------------------------------------
>
> > respec@7.2.1 copydeps /Users/dan/w3c/webrtc-pc/support/respec
> > node ./tools/copydeps.js
>
> /Users/dan/w3c/webrtc-pc/support/respec/tools/copydeps.js:30
> const rm = async(function*(...files) {
>                            ^^^
>
> SyntaxError: Unexpected token ...
>     at exports.runInThisContext (vm.js:53:16)
>     at Module._compile (module.js:373:25)
>     at Object.Module._extensions..js (module.js:416:10)
>     at Module.load (module.js:343:32)
>     at Function.Module._load (module.js:300:12)
>     at Function.Module.runMain (module.js:441:10)
>     at startup (node.js:139:18)
>     at node.js:968:3
>
> npm ERR! Darwin 16.1.0
> npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "copydeps"
> npm ERR! node v4.4.6
> npm ERR! npm  v2.15.5
> npm ERR! code ELIFECYCLE
> npm ERR! respec@7.2.1 copydeps: `node ./tools/copydeps.js`
> npm ERR! Exit status 1
>
>
> On Thu, Dec 22, 2016 at 8:27 AM, Daniel Burnett <danielcburnett@gmail.com>
> wrote:
>
>> Ah, I see.  Your issue #978 lists all the parts of Travis that are now
>> failing.  Which is weird, because I got a Travis success on my build!
>>
>> On Thu, Dec 22, 2016 at 8:24 AM, Daniel Burnett <danielcburnett@gmail.com
>> > wrote:
>>
>>> Travis seems to be failing (for some non-obvious reason) on your PR
>>> 977.  Can you please check?
>>>
>>> -- dan
>>>
>>>
>>> On Tue, Dec 20, 2016 at 6:48 PM, Vivien Lacourba <vivien@w3.org> wrote:
>>>
>>>> [Moving to editors list]
>>>>
>>>> Hi Dan,
>>>>
>>>> On Mon, 2016-12-19 at 15:02 -0500, Daniel Burnett wrote:
>>>> > A new dated version of the Editors' draft is available.
>>>> >
>>>> > Dated version: https://w3c.github.io/webrtc-pc/archives/20161219/webr
>>>> > tc.html
>>>> > Living document: https://w3c.github.io/webrtc-pc/
>>>>
>>>> This latest push to gh-pages did not generated a new TR draft as there
>>>> were some HTML issues detected in the new editors draft.
>>>>
>>>> See:
>>>> https://lists.w3.org/Archives/Public/public-tr-notifications/2016Dec/00
>>>> 82.html
>>>> <https://lists.w3.org/Archives/Public/public-tr-notifications/2016Dec/0082.html>
>>>> and:
>>>> https://validator.w3.org/nu/?doc=https%3A%2F%2Fw3c.github.io%2Fwebrtc-p
>>>> c%2F
>>>> <https://validator.w3.org/nu/?doc=https%3A%2F%2Fw3c.github.io%2Fwebrtc-pc%2F>
>>>>
>>>> I fixed those in a new PR:
>>>> https://github.com/w3c/webrtc-pc/pull/977
>>>>
>>>> While doing this I noticed some new respec warnings and errors (which I
>>>> don't think relates to this new PR 977). I created a new issue for that
>>>> https://github.com/w3c/webrtc-pc/issues/978
>>>>
>>>> Note that once the markup and respec issues are fixed you will need to
>>>> push again to gh-pages to trigger a new TR draft publication.
>>>>
>>>> Thanks,
>>>> Vivien
>>>>
>>>> --
>>>> Vivien Lacourba                      World Wide Web Consortium
>>>> vivien@w3.org                        http://www.w3.org
>>>> http://www.w3.org/People/Vivien      Tel: +33.4.92.38.78.89
>>>>
>>>
>>>
>>
>