W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2015

Re: Travis now enabled

From: Joe Berkovitz <joe@noteflight.com>
Date: Fri, 16 Oct 2015 15:31:52 -0400
Message-ID: <CA+ojG-bGDUze=kwJvj1NrdvdtTmtyMkQZhnn--ou1n16jOrGLQ@mail.gmail.com>
To: Paul Adenot <padenot@mozilla.com>
Cc: "public-audio@w3.org Group" <public-audio@w3.org>

Is there some way to have the diff command in the travis git hook script
not be -q, but show the diff output? That would help quickly identify the
problem in Github's build output for those of us who don't have the whole
Travis environment set up.

Right now all we see is something like this (imagine a wa-wa-waah "fail"
sound effect as accompaniment):


On Fri, Oct 16, 2015 at 12:07 PM, Paul Adenot <padenot@mozilla.com> wrote:

> Group,
> I went ahead an enabled travis-ci on the web-audio-api repo. It ensure
> that the spec is neatly indented and has valid markup using the tidy
> program.
> You can replicate the testing environment that runs on the test machines
> by running (on an UNIX machine that has git and cmake):
> $ make install_tidy
> $ make check
> and if this fails, you can do
> $ make tidy
> to call tidy with the appropriate options. Reading the tidy config file,
> you can see what the rules are (it's pretty self explanatory and standard).
> I've added a badge to the readme that tells us whether the current spec is
> clean or not. More over, when opening a pull request, a nice bot will come
> and tell you whether it's tidy-clean or not, and then you can push a
> followup as needed.
> It might spam us with emails, we'll see (I'm actually not sure if I'm the
> one receiving them or what).
> Cheers, and have a good weekend,
> Paul.

.            .       .    .  . ...Joe

*Joe Berkovitz*

*Noteflight LLC*
49R Day Street / Somerville, MA 02144 / USA
phone: +1 978 314 6271
"Your music, everywhere"
Received on Friday, 16 October 2015 19:32:26 UTC

This archive was generated by hypermail 2.3.1 : Friday, 18 December 2015 09:00:35 UTC