----- Forwarded Message -----
| From: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
| To: "infra" <infra(a)ovirt.org>
| Cc: "David Caro Estevez" <dcaroest(a)redhat.com>
| Sent: Monday, August 12, 2013 10:58:04 AM
| Subject: running network functional tests
| Hello everbody!
| Just recently we added networking functional tests and we would like
| to have them running when we submit patches network related, i.e.
| going to affect network modules. Displaying success or failure
| as it happens with the current unittests.
| - OS Fedora 19/RHEL6.4 should not matter.
| - Kernel module used: bonding, dummy.
| - No more than one 'instance' of networkTests should run
| on a specific host, simply because we use some global
| constants to identify network name vlan id and so on.
| - Ideally we can use a previously proposed idea of commit tag
| where for example @networking is provided in the commit msg
| title to identify the need of running also the network
| functional tests.
| - We should be able to run at the same time functional networking
| tests and unit tests - I don't expect any conflicts.
| Would be cool to have a test run before -1s all networking patches
| in case of problems :-)
| Let me know if more information are needed.
| Cheers, Giuseppe
Is there any update on the subject?
Any estimate to have functional network tests running?
I mind that we can run network functional tests upstream
that will speed up our workflow and possibly decrease the