On 05/07/2017 22:46, Cillian O'Donnell wrote: > > Now the thing is, I might have to run RTEMS Tester about 3 times for > the full testsuite before I can get the report, as the covoar runs > will often hang on an arbitrary method and have to be manually exited > and re-run.
How is covoar being run? Is it being run by the 'rtems-test' command? > The point that this happens is not repeatable and there's > no error message to go on. Is it the covoar process that is stopping? Is it the process idle or using 100%? > The only common theme is the methods will > often be called thread...something. Even more rarely it will stop with > the message 'resource temporarily unavailable'. I'm wondering is this > normal behaviour for covoar on a long test-run? This never happens > when running just the samples. It is not normal behavior. > > When a test run is successful it will also finish with a lot of these > messages: > > *** Trace block is inconsistent with coverage map > *** Trace block (0x4000c4fc - 0x4000c51f) for 36 bytes > *** Coverage map /home/cpod/coverage_test/test/coverage/unlimited.exe.cov > INFO: DesiredSymbols::mergeCoverageMap - Unable to merge coverage map > for _Thread_queue_Extract_with_proxy because the sizes are different I wonder what sizes are different? Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
