xen regression test

xen regression test

[Kip Macy]

[-- Attachment #1.1: Type: text/plain, Size: 272 bytes --]

I was looking at the results of the runs at:

http://xenbits.xensource.com/xenrt/

It looks like many of the tests never get run and some of those that are
getting run are skipped at times. What determines which tests are getting
run and which are skipped?

-Kip

[-- Attachment #1.2: Type: text/html, Size: 375 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: xen regression test

[James Bulpin]

Kip Macy wrote:
> I was looking at the results of the runs at:
> 
> http://xenbits.xensource.com/xenrt/
> 
> It looks like many of the tests never get run and some of those that are 
> getting run are skipped at times. What determines which tests are 
> getting run and which are skipped?

The matrix axes contains tests that have not yet been written and/or 
integrated into the harness. This includes all of phases 5 and 6 and a 
few tests elsewhere such as crashme.

Tests will be skipped for two reasons. Firstly if we want to 
"fast-forward" to test something late in the sequence and we don't want 
to wait for everything preceding it to run (this often happens to verify 
that a specific bug fix has worked). Secondly if a test is not valid for 
that particular combination of machine/architecture/version etc.. For 
example we now skip tbench and dbench on x86-64 because they don't build 
on that architecture and we've not had time to fix them.

James