Re: skip-if(verify)

2018-03-07 Thread Gabriele Svelto
ny tests were written pre-test-verify, and don't clean > up correctly to deal with multiple runs in the same process. They work fine > when running as a single session, but blow up in TV. Having skip-if(verify) > means that we can at least mark those tests as known broken on TV witho

Re: skip-if(verify)

2018-03-06 Thread Emilio Cobos Álvarez
On 03/06/2018 08:05 PM, Kyle Machulis wrote: > In my experience, many tests were written pre-test-verify, and don't clean > up correctly to deal with multiple runs in the same process. They work fine > when running as a single session, but blow up in TV. Having skip-if(verify) >

Re: skip-if(verify)

2018-03-06 Thread Kyle Machulis
In my experience, many tests were written pre-test-verify, and don't clean up correctly to deal with multiple runs in the same process. They work fine when running as a single session, but blow up in TV. Having skip-if(verify) means that we can at least mark those tests as known broken

Re: skip-if(verify)

2018-03-06 Thread Emilio Cobos Álvarez
On 03/06/2018 06:04 PM, Geoffrey Brown wrote: > It is now possible to skip tests in test-verify. Simplify annotate the > manifest for your test: > > [test] > skip-if = verify > > or, for reftests: > > skip-if(verify) ... > > and the test-verify (TV) tes

skip-if(verify)

2018-03-06 Thread Geoffrey Brown
It is now possible to skip tests in test-verify. Simplify annotate the manifest for your test: [test] skip-if = verify or, for reftests: skip-if(verify) ... and the test-verify (TV) test task will not try to verify the annotated test. Please don't abuse this feature! Most TV failures ind