On Fri, 18 May 2018, 14:55 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com> wrote:
> > > On 18 May 2018 at 19:09, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > >> >> >> On Fri, 18 May 2018, 12:36 Vijay Kumar Banerjee, < >> vijaykumar9...@gmail.com> wrote: >> >>> >>> On 18 May 2018 at 12:30, Cillian O'Donnell <cpodonne...@gmail.com> >>> wrote: >>> >>> >>>> Cool, you should run it for the full testsuite and take a look at that >>>> report (takes a while.. around 575 tests) >>>> >>>>> >>>>>> When I try to run the full testsuites it gives the following error . >>> What could be causing this ? >>> >> >> If you run the full testsuite without the coverage options, does it still >> happen? >> > No it seems to run fine without coverage. > I vaguely remember seeing this before last year, I suspect that when things are cleared up in coverage.py it will dissappear. So don't worry about it for now, carry on with what you're doing. What branch are you working on at the moment? > >>> ------------------- >>> self.__bootstrap_inner() >>> File "/usr/lib64/python2.7/threading.py", line 817, in >>> __bootstrap_inner >>> (self.name, _format_exc())) >>> IOError: [Errno 11] Resource temporarily unavailable >>> >>> >> >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
