On 06/10/2014 11:47 PM, Lucas Meneghel Rodrigues wrote:
Ok, somehow I did miss this email.We don't have a way to do what you want currently, although I started to formulate how to do so in autotest. I would lean towards doing the following: 1) Create a new job status EXPECTED_FAIL or similar on client/shared/base_job.py 1) Create an ExpectedFailure() exception class inside client/shared/error.py, possibly inheriting from TestWarning 2) Create a decorator called expected_failure or whatever in some library, that wraps the called function, and if it raises an exception, it traps it and throws the expected error failure. Now the tricky parts should be checking what is necessary to make web UI and the such to display the test in a non fatal way. In autotest, even TestWarnings are considered failures, since you can't really know on a quick glance if the test passed or simply had an expected failure just by glancing at happily green painted cells. Unfortunately I can't really say I'm going to commit time to work on it, as I can barely read email and do minimal maintenance in virt-test and autotest these days with all the rush coding our new project.
Ok, at lease it is important to know the status quo in Autotest at the moment.
In other news, your comment about the run_tests() function, that's an old bug that you hit. I did send a fix in: https://github.com/autotest/virt-test/pull/1697
Very good, I am glad it was already spotted. Thanks Lucas!
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
