> I thought of option 3, but 2 would be nice. > I guess compilation will fail in most of the cases it has to. And > adding an option to define a test result as not_applicable could > handle cases where compilations works but should not.
Done. If you look at the last testing_matrix.yaml file, it has been generated automatically. * compile(board + test) == ok: keep the file * compile(board + test) != ok: discard it (BTW, jalv2 2.4h now returns none 0 status code when errors, this is so much easier...) As expected, 16f648a + i2c hardware failed :) Seb -- Sébastien LELONG http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
