Hi Joep, > 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.
OK, I'll do this, this souldn't be too complicated. Format changes must be expected in the YAML file, probably to specify longer path to samples and tests + boardfile used, etc... But this shouldn't be too complicated. > The script should also take the test results entered in the old file > and put it in the new file, when (after) it is generated. If this is > not possible, we should not regenerate the yaml file. This case is alreasy handled: when you update the matrix, if the file exists, then it generate the new matrix then put back results from previous. If the file doesn't exist, it just create a fresly new matrix. This is the same when merging two matrices. 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 -~----------~----~----~----~------~----~------~--~---
