From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bulpin Subject: Re: xen regression test Date: Thu, 22 Sep 2005 21:14:36 +0100 Message-ID: <433310AC.7020701@xensource.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kip Macy Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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