From: Domenico Andreoli <domenico.andreoli@linux.com>
To: ltp@lists.linux.it
Subject: [LTP] q-rig: qemu ltprun on armhf and arm64
Date: Tue, 11 Apr 2017 17:08:20 +0200 [thread overview]
Message-ID: <20170411150820.GA31990@localhost> (raw)
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
next reply other threads:[~2017-04-11 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 15:08 Domenico Andreoli [this message]
2017-04-12 9:07 ` [LTP] q-rig: qemu ltprun on armhf and arm64 Cyril Hrubis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170411150820.GA31990@localhost \
--to=domenico.andreoli@linux.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox