From mboxrd@z Thu Jan  1 00:00:00 1970
From: Domenico Andreoli <domenico.andreoli@linux.com>
Date: Tue, 11 Apr 2017 17:08:20 +0200
Subject: [LTP] q-rig: qemu ltprun on armhf and arm64
Message-ID: <20170411150820.GA31990@localhost>
List-Id: <ltp.lists.linux.it>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ltp@lists.linux.it

Hi all,

  this is me, Domenico (cavokz on github.com, cavok at debian.org).

I've been toying with Travis CI, qemu and LTP recently. My
effort is here: https://github.com/q-rig. It runs LTP on top
of the latest linux -rc on Debian sid, inside qemu on armhf and
arm64. Binaries are built when needed. You can find them here:
https://github.com/q-rig/qemu-ltprun-results.

Activities are run in Travis CI [0]. LTP tests are split so to finish
in less than 49 minutes (Travis CI constraint). The LPT results are
put again in https://github.com/q-rig/qemu-ltprun-results, which is
probably the wrong place.

All this is quite brute force cpu cycles harvesting generously proved
by Travis CI and github.

Now I'd like to tackle the aggregation of the data generated by LTP. The
best I could do is just generating also the .html page and upload it
to github [1] but I think more is actually desirable here.

Is there any documentation I'm expected to read before asking for
support here? :)

Thanks,
Domenico

[0] https://travis-ci.org/q-rig/qemu-ltprun
[1] https://github.com/q-rig/qemu-ltprun-results/tree/master/ltp/20170411-3.10-linux-4.11.0-rc6-ltp-20170116-arm64

-- 
3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13