> irrespective of if the last one failed, and collate the failed tests > to report at the end. This helps when developing fixes for something, > which may fix what you're focusing on but then cause failures > elsewhere. > > Maybe we ought to write out a little regression run report which > indicates the tests which were run and those which failed?
The orbuild project I wrote has a tool to collect run reports and generate a combined report in HTML. Alternatively, ORPSoCV2 could use DejaGnu, like or1ksim does, which implements that kind of behaviour. I don't think I'll have time to take on this task. Until someones does it, I would still apply my patch. Otherwise, test errors go easily unnoticed, which is in my oppinion worse than stopping on the first error. Best regards, Ruben _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
