> On Fri, 10 Jan 2014 03:58:06 +0100 (CET) > [email protected] wrote: > > For FreeBSD, I'd like to see this issue fixed, but I don't really > > know > > how to help. > > > > I will start tinkering with the test-suite this evening. I've been > thinking about writing a testing driver script that will launch > [parallel][1] jobs and go through the entire test-suite, regardless > of > any particular failures, then assemble a nicely formatted report. > > [1]: http://www.gnu.org/software/parallel/ > > Once we see which tests (of the complete set) ghdl-freebsd passes and > which tests it fails, there might be a pattern that indicates what > the problem might be.
Three notes: * although the tests in gna/ are independent, some of vests aren't: there are tests that need to be analysed or run after others. So running them in parallel isn't trivial at all. * Running the whole test suite and finding a pattern is a good idea. This often ease finding the issue. * Don't spend to much time in trying to run in parallel: your objective is to run the whole test suite first. With mcode, the whole test suite runs in a couple of minutes. Tristan. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
