From: Dario Faggioli <dario.faggioli@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Call to write tests for osstest
Date: Fri, 9 Aug 2013 13:19:54 +0200 [thread overview]
Message-ID: <1376047194.19531.112.camel@Solace> (raw)
In-Reply-To: <1369957247.20130808193221@eikelenboom.it>
[-- Attachment #1.1: Type: text/plain, Size: 1253 bytes --]
On gio, 2013-08-08 at 19:32 +0200, Sander Eikelenboom wrote:
> * Some performance testing (network, block, cpu/mem/fork/real apps benchmarks, some other metrics)
> - perhaps makes separate graphs of these, so one can see performance increase or decrease over a larger time frame, and see at around what commits that occurred.
> - only after all basic tests succeeded and a push was done.
>
We are after this too. I am looking at how to make it possible to do
something like that on top of OSSTest.
Perf benchmarking is a little bit different from regression
smoke-testing, but still I think (hope? :-)) that most of the
infrastructure can be reused.
Also, what hardware to use and how to properly schedule these kind of
"tests" is something that needs a bit more of thinking/discussion, I
think.
Anyway, although I'm not committing to have all it 100% ready for 4.4,
George, feel free to add this to your tracking list and put m name on
it.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-09 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 16:01 Call to write tests for osstest George Dunlap
2013-08-08 17:32 ` Sander Eikelenboom
2013-08-08 19:42 ` Konrad Rzeszutek Wilk
2013-08-09 11:19 ` Dario Faggioli [this message]
2013-08-09 11:46 ` Sander Eikelenboom
2013-08-09 12:00 ` Wei Liu
2013-08-09 12:04 ` Sander Eikelenboom
2013-08-09 12:16 ` Dario Faggioli
2013-08-14 15:03 ` George Dunlap
2013-08-08 17:37 ` Sander Eikelenboom
2013-08-14 13:51 ` George Dunlap
2013-08-08 19:40 ` Konrad Rzeszutek Wilk
2013-08-14 13:52 ` George Dunlap
2013-08-13 14:24 ` Ben Guthro
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=1376047194.19531.112.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.