[Mesa-dev] [PATCH] travis: Initial import of travis instructions.

Rob Clark robdclark at gmail.com
Sat Nov 28 10:29:14 PST 2015


On Tue, Nov 24, 2015 at 4:38 PM, Rob Clark <robdclark at gmail.com> wrote:
> On Tue, Nov 24, 2015 at 4:10 PM, Eric Anholt <eric at anholt.net> wrote:
>> Rob Clark <robdclark at gmail.com> writes:
>>
>>> On Tue, Nov 24, 2015 at 2:10 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
>>>> Any reason not to add freedreno and nouveau in here?
>>>>
>>>> Too bad these packages don't all have "latest" symlinks...
>>>
>>> hmm, I was going to say that tinderbox can figure out how to just
>>> build latest (plus we at one point had builders for several different
>>> arch's for xserver and mesa, etc..)
>>>
>>> but then I noticed that http://tinderbox.x.org/ is in kind of dire shape.. :-(
>>
>> I've run tinderbox servers before.  It's a bunch of work, and then
>> nobody looks at it anyway, including me.  It also only tests your pushes
>> once they've hit master, which to me misses the whole point.
>>
>> The github integration means that people doing things on github see CI
>> state in their interfaces (well, in pull requests.  If you just want
>> current state, you have to go to the travis-ci.org dashboard).  It also
>> sends me emails when my branch pushes fail.
>
> yeah, I've run tinderbox builder too, so I know the issues..
>
> All the same, it's probably still a good idea to resurrect tinderbox
> to get build coverage on different archs..  the clever thing would be
> if we could also work in piglit runs as well (ie. at least for
> whatever gpu(s)) the various builders have..

In related news, I've managed to get an armv7 builder going again..

  http://tinderbox.x.org/builds/machines/robclark-reptile/

it's building freedreno+vc4 gallium drivers, along w/
freedreno/armsoc/omap/modesetting ddx, etc.  Once etnaviv finds it's
way to upstream I'll switch it on as well.

I guess I should try and figure out enough jhbuild to trick it into
building/running piglit after mesa, then we could at least get some
piglit coverage on one device.

I do have one armv8 device that I could perhaps spare for an armv8
builder, but short a spare power supply for that one so would have to
unplug it from time to time.. which would be a bit annoying.  If
someone has some armv8 hw to dedicate to the cause, I could send you
my notes/config..

BR,
-R

> It may just end up being best to have both, at least as long as this
> is low effort to keep going, it doesn't hurt.  And the convenience for
> personal git trees is a win.
>
> BR,
> -R


More information about the mesa-dev mailing list