RE: [webrtc-stats] Travis appears to be borked again

I believe this has resulted from a respec.js change, not Travis, because we are seeing the same errors elsewhere (WebRTC-pc, ORTC, etc.)

________________________________________
From: Harald Alvestrand via GitHub [sysbot+gh@w3.org]
Sent: Monday, January 2, 2017 6:10 AM
To: public-webrtc@w3.org
Subject: [webrtc-stats] Travis appears to be borked again

alvestrand has just created a new issue for
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-stats&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C521106b7dfac43076deb08d4330048ce%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636189523691837560&sdata=QKvD5qDgCfYl8Ob%2BvXHi8oq%2FQoBmuj%2BHgllUlkV7%2FIA%3D&reserved=0:


== Travis appears to be borked again ==
Running this command:

node support/respec/tools/respec2html.js -e --src
file://`pwd`/webrtc-stats.html --out build/output.html

will produce the output:

🚨 ReSpec warn: No <dfn> for timestamp in RTCStats.
🚨 ReSpec warn: No <dfn> for type in RTCStats.
🚨 ReSpec warn: No <dfn> for id in RTCStats.
🚨 ReSpec warn: No <dfn> for RTCStats.
🚨 ReSpec warn: No <dfn> for RTCCertificateStats.
undefined

In Travis, this causes failure.
"make update" gave no improvement.

Help sought - tagging @vivienlacourba @dontcallmedom

Please view or discuss this issue at
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-stats%2Fissues%2F124&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C521106b7dfac43076deb08d4330048ce%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636189523691847567&sdata=n0Ltb8w4TsxkMUjumMWGWwzUigCI8%2FzqNNpi0eYZmq4%3D&reserved=0 using your GitHub
account

Received on Monday, 2 January 2017 23:17:04 UTC