[Bug 658912] Integrate with LAVA

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=658912
  GStreamer | gst-qa-system | unspecified

David Laban <alsuren> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #4 from David Laban <alsuren at gmail.com> 2011-09-21 13:09:43 UTC ---
Merged to master and packaged in my PPA

== Steps to test using schroot ==

$ sudo debootstrap --arch i386 --verbose natty /srv/chroot/natty-i386 \
    http://archive.ubuntu.com/ubuntu
# This isn't a secure chroot: it's a scratch area with enough
# information to make ubuntu behave itself and reduce the number
# of moving parts in the test system.
# A malicious program would be able to break out easily.
$ sudo mount -o bind /proc /srv/chroot/natty-i386/proc
$ sudo mount -o bind /dev /srv/chroot/natty-i386/dev
$ sudo mount -o bind /sys /srv/chroot/natty-i386/sys
$ echo "
[natty-i386]
personality=linux32
root-users=$USER" | sudo tee --append /etc/schroot/schroot.conf

$ sudo cp /etc/shadow /etc/passwd /etc/group /etc/resolv.conf /etc/hosts \
    /srv/chroot/natty-i386/etc/
$ sudo mkdir /srv/chroot/natty-i386/$HOME
$ sudo chown $USER /srv/chroot/natty-i386/$HOME

# Now chroot in and run the tests.
$ (cd && schroot -p -c natty-i386 bash)

$ sudo apt-get install python-software-properties python-setuptools
$ sudo apt-add-repository http://archive.ubuntu.com/ubuntu universe
$ sudo apt-add-repository ppa:alsuren/linaro
$ sudo apt-get update
$ bzr branch lp:~alsuren/lava-test/insanity
$ cd insanity
$ setup.py develop
$ lava-test install insanity
$ lava-test dashboard setup $http://$SERVER/launch-control/
$ lava-test run insanity # and copy-paste $RESULT below
$ lava-test dashboard put /anonymous/$STREAM/ $RESULT

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.