On Tue, 10 May 2011 08:31:08 +0200 (CEST) Julia Lawall <[email protected]> wrote:
> > Why it expects 337 passed tests and why it didn't fail in the first run? > > It's interesting, that if I enable python things go back to normal. > > Looks like a bug. ... > The use of yes then updates the expected score to what was obtained on the > first run. A program "no" would thus be a better choice than "yes" for > this kind of test, if you want to stay with the original results. > > Then the problem is that there are some tests that include python. > Because these tests have succeeded at some time in the past, they are > still considered as potential successful tests, even though they did not > succeed in the most current run. Thus, the current run has 335 successful > tests and 337 expected. Ah, so answering "yes" not just substitutes with local success result, but joins all currently and previously passed tests. Yeah, would be cool to have a bit smarter -testall which would 'SKIP' tests and avoid evpecting them to pass if feature does not present. Thanks detailed explanation! -- Sergei
signature.asc
Description: PGP signature
_______________________________________________ Cocci mailing list [email protected] http://lists.diku.dk/mailman/listinfo/cocci (Web access from inside DIKUs LAN only)
