[Piglit] Building current piglit on ubuntu 12.04?

Ilia Mirkin imirkin at alum.mit.edu
Mon Sep 5 21:18:23 UTC 2016

On Mon, Sep 5, 2016 at 5:04 PM, Dan Kegel <dank at kegel.com> wrote:
> OK, now that I know the python3 requirement is soft, here's how I got
> current piglit running on ubuntu 12.04.
>         sudo apt-get install -y python-dev python-nose python-six
> python-numpy python-matplotlib
>         # ubuntu 12.04's matplotlib is too old, as are some of its dependencies
>         # Install it anyway via apt to get dependencies, then update
> what's needed.
>         sudo apt-get remove -y python-six python-numpy
> python-matplotlib python-pyparsing python-mako
>         # purge any locally installed modules.  Careful.
>         rm -rf $HOME/.local/lib/python*
>         # Work around error from pip install.
>         sudo /usr/bin/easy_install -U distribute
>         # Carefully install barely new enough versions of a few things
>         pip install --user pyparsing==1.5.6
>         pip install --user numpy==1.7.0   # required by piglit's CMakeLists.txt
>         pip install --user matplotlib==1.4.3
>         export PYTHONPATH=$HOME/.local/lib/python2.7:$PYTHONPATH:/usr/lib/python2.7
>         cmake -DPIGLIT_USE_WAFFLE=False

I think you forgot a "make -jN" step here. Also I'm surprised things
work well without waffle.

>         python2 piglit run -1 -t texture tests/quick results/quick

Quick is a misnomer. What it really means is "all minus a small
handful of *super slow* tests". Perhaps it should be renamed to
tests/not_as_incredibly_slow_as_all. Normally I just run tests/gpu
which gets rid of all the parser/etc tests. [Since I tend not to muck
around in that stuff, but I guess if you're trying to get at overall
driver quality, it seems reasonable to include them.]

>         python2 piglit summary console results/quick
> I'm using trivial backports of packages linux-generic-lts-utopic and
> nvidia-352 for the kernel and nvidia drivers,
> and lspci says my graphics card is GF110 [GeForce GTX 570].
> It still crashes the system nearly instantly with a fairly recent
> nvidia card and driver, yay closed source.

Even with the -1, on just the texturing tests? That sounds like
something is horridly wrong.

> I may try to narrow that down some more and blacklist the tests that
> break the system,
> or I may switch to the AMD W600 and catalyst, which is close to
> another configuration I care about.
> Or I might switch to only testing on ubuntu 16.04 for a while, where
> things seem more stable,
> and just hope Ubuntu 12.04 vanishes in a puff of greasy black smoke soon.
> In any case, I'll probably move to a non-RAID system for testing (!).
> Watching the RAID rebuild itself
> after a graphics driver crash is no fun.

You may be interested in nfsroot. I use it for all my arm boards, as
well as a PPC G5. Makes crashing them a much less frustrating


More information about the Piglit mailing list