[OE-core] [PATCH 3/3] runtime/cases/ptest.py: fail when ptests fail on target

[Alexander Kanavin]

On 12/20/2017 07:23 PM, Burton, Ross wrote:
> So the context was that so many ptests were failing that the test 
> couldn't be done automatically and expected to succeed. Bugs were filed 
> and the problem chipped away at, but last I looked it wasn't in a state 
> to be enabled.
> 
> If a core-image-sato passes with ptests enabled then that's great, but 
> I'll be surprised if it does!

It doesn't. In fact, it never finishes, because bluez ptest hangs 
forever. That shouldn't be a problem though, because ptests are not 
included by default in any of the standard images, and so the test is 
simply skipped (see patch 1 of 3). The point of this patch is to 
eliminate misleading passing behaviour when people do include ptests - 
either for everything in their image or for specific packages they 
maintain, and want, for example, to check for regressions on version 
upgrades.

Alex