- From: Daniel Burnett <danielcburnett@gmail.com>
- Date: Thu, 5 Jan 2017 09:49:07 -0500
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: Bernard Aboba <Bernard.Aboba@microsoft.com>, Dominique Hazael-Massieux <dom@w3.org>, Vivien Lacourba <vivien@w3.org>, "public-webrtc-editors@w3.org" <public-webrtc-editors@w3.org>
- Message-ID: <CA+EnjbK8JzgzdHYC_FgvWn=Ds4nThPB-eDfQRv7zWa8WE2vx0A@mail.gmail.com>
Yes, the 'no <dfn> for' error is the one. It is now showing up in places
that used to work (without those dfns).
We can request they do more testing, but ultimately the only real control
we have is to point to specific numbered versions. It's a nuisance, but it
would keep us from having our specs fail suddenly (and unexpectedly) due to
changes they make.
-- dan
On Thu, Jan 5, 2017 at 2:25 AM, Harald Alvestrand <harald@alvestrand.no>
wrote:
> Den 03. jan. 2017 19:04, skrev Bernard Aboba:
> > I am still seeing respect errors galore:
> > https://rawgit.com/w3c/webrtc-pc/master/webrtc.html
>
> They all seem to be "no <dfn> for....", indicating that a new check has
> been added.
>
> I got exactly one of those in the stats spec (+ 4 where I know why they
> happen), and spent long minutes trying to figure out how the markup for
> that variable differed from the others. Failed.
>
> The respec maintenance team seems to take a dim view of backwards
> compatibility; we can either grow defensive and point to numbered respec
> versions, or get them to be proactive and not introduce new tests until
> they either have them running across a significant number of tip-of-tree
> specs without new errors, or have done explicit outreach to tell us why
> the error counts increase and how to fix them.
>
>
> > ________________________________________
> > From: Dominique Hazael-Massieux [dom@w3.org]
> > Sent: Tuesday, January 3, 2017 8:47 AM
> > To: Daniel Burnett; Vivien Lacourba
> > Cc: public-webrtc-editors@w3.org
> > Subject: Re: New webrtc-pc Editor's draft (v20161219)
> >
> > There was a buggy release of respec - I believe it should be fine now.
> >
> > With regard to your earlier error ("Unexpected token ..."), you need to
> > use node v6 or more to run the respec command line.
> >
> > Dom
> >
> > On 22/12/2016 15:27, Daniel Burnett wrote:
> >> 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 <mailto: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 <mailto: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 <mailto: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 <mailto: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://na01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%
> 2Fwebrtc-pc%2Farchives%2F20161219%2Fwebr&data=02%7C01%7CBernard.Aboba%
> 40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915070837&sdata=
> H1PwLDFIuksGfZGxRKV72GpBF6biskoiFJl0RZtFwmM%3D&reserved=0
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fw3c.github.io%2Fwebrtc-pc%2Farchives%
> 2F20161219%2Fwebr&data=02%7C01%7CBernard.Aboba%40microsoft.com%
> 7C35675f0022c04b26db2008d433df2772%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636190480915070837&sdata=H1PwLDFIuksGfZGxRKV72GpBF6bisk
> oiFJl0RZtFwmM%3D&reserved=0>
> >> > tc.html
> >> > Living document: https://na01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%
> 2Fwebrtc-pc%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%
> 7C35675f0022c04b26db2008d433df2772%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636190480915070837&sdata=RCWN94wqW3%2B2Hlfz%2FIrtAwvC%
> 2FGI8bs%2BcUy8OOOR0uCI%3D&reserved=0
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fw3c.github.io%2Fwebrtc-pc%2F&data=02%7C01%
> 7CBernard.Aboba%40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915070837&sdata=
> RCWN94wqW3%2B2Hlfz%2FIrtAwvC%2FGI8bs%2BcUy8OOOR0uCI%3D&reserved=0>
> >>
> >> 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://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-
> tr-notifications%2F2016Dec%2F00&data=02%7C01%7CBernard.
> Aboba%40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915070837&sdata=Xf%
> 2FOcl%2BwJWvgdWnABsjQUpwpwf0Og2WIH0feSx4DAS0%3D&reserved=0
> >> 82.html
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-
> tr-notifications%2F2016Dec%2F0082.html&data=02%7C01%
> 7CBernard.Aboba%40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915080845&sdata=
> roB8aPmZ3o6WtXm239FjJD50t1CHOHrE5UbBOe8UYGY%3D&reserved=0>
> >> and:
> >> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fvalidator.w3.org%2Fnu%2F%3Fdoc%3Dhttps%
> 253A%252F%252Fw3c.github.io%252Fwebrtc-p&data=02%7C01%
> 7CBernard.Aboba%40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915080845&sdata=
> NO7Q1Ct45YsKzOdPrub2jUhTFzOBCOCRThZKSf5H75A%3D&reserved=0
> >> c%2F
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fvalidator.w3.org%2Fnu%2F%3Fdoc%3Dhttps%
> 253A%252F%252Fw3c.github.io%252Fwebrtc-pc%252F&data=02%
> 7C01%7CBernard.Aboba%40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915080845&sdata=
> lAdul9NlQFXkOUINxbj8BrchK68NVZc%2FGK%2Br69UmwdM%3D&reserved=0>
> >>
> >> I fixed those in a new PR:
> >> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-pc%2Fpull%
> 2F977&data=02%7C01%7CBernard.Aboba%40microsoft.com%
> 7C35675f0022c04b26db2008d433df2772%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636190480915080845&sdata=r0D3MHY71qHtEeWkGJWT9tVBznti%
> 2B44IxYkJYAdt0wY%3D&reserved=0
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-pc%2Fpull%
> 2F977&data=02%7C01%7CBernard.Aboba%40microsoft.com%
> 7C35675f0022c04b26db2008d433df2772%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636190480915080845&sdata=r0D3MHY71qHtEeWkGJWT9tVBznti%
> 2B44IxYkJYAdt0wY%3D&reserved=0>
> >>
> >> 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://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-pc%2Fissues%
> 2F978&data=02%7C01%7CBernard.Aboba%40microsoft.com%
> 7C35675f0022c04b26db2008d433df2772%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636190480915080845&sdata=G0G6uH1TDJGu3RZIBTC4p1rMq64Qwb
> ud5jgkjDas2i4%3D&reserved=0
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-pc%2Fissues%
> 2F978&data=02%7C01%7CBernard.Aboba%40microsoft.com%
> 7C35675f0022c04b26db2008d433df2772%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636190480915080845&sdata=G0G6uH1TDJGu3RZIBTC4p1rMq64Qwb
> ud5jgkjDas2i4%3D&reserved=0>
> >>
> >> 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 <mailto:vivien@w3.org>
> >> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.w3.org&data=02%7C01%7CBernard.Aboba%40microsoft.com%
> 7C35675f0022c04b26db2008d433df2772%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636190480915080845&sdata=lefEC1FNQCRG0qTk0lIId%
> 2FMEEJghNpDSBZTwmccTBd4%3D&reserved=0
> >> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.w3.org%2FPeople%2FVivien&data=02%7C01%7CBernard.Aboba%
> 40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915080845&sdata=
> eFiizMrkGlTHzawLxovYV0nirKtJuiJlIJ2IgoOYLtg%3D&reserved=0
> >> <https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.w3.org%2FPeople%2FVivien&data=02%7C01%7CBernard.Aboba%
> 40microsoft.com%7C35675f0022c04b26db2008d433df2772%
> 7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636190480915080845&sdata=
> eFiizMrkGlTHzawLxovYV0nirKtJuiJlIJ2IgoOYLtg%3D&reserved=0> Tel:
> >> +33.4.92.38.78.89 <tel:%2B33.4.92.38.78.89>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
>
Received on Thursday, 5 January 2017 14:50:23 UTC