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
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)
>
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
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
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
5 matches
Mail list logo