Re: covoar SIGKILL Investigation

On 22/08/2018 14:41, Joel Sherrill wrote: > On Tue, Aug 21, 2018, 10:26 PM Chris Johns > wrote: > > On 22/08/2018 09:29, Joel Sherrill wrote: > > On Tue, Aug 21, 2018, 4:05 PM Vijay Kumar Banerjee > mailto:vijaykumar9...@gmail.com> > >

Re: covoar SIGKILL Investigation

On Tue, Aug 21, 2018, 10:26 PM Chris Johns wrote: > On 22/08/2018 09:29, Joel Sherrill wrote: > > On Tue, Aug 21, 2018, 4:05 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com > > > wrote: > > On Wed, 22 Aug 2018 at 01:55, Joel Sherrill >

Re: covoar SIGKILL Investigation

On 22/08/2018 09:29, Joel Sherrill wrote: > On Tue, Aug 21, 2018, 4:05 PM Vijay Kumar Banerjee > wrote: > On Wed, 22 Aug 2018 at 01:55, Joel Sherrill > wrote: > > How long is covoar taking for the entire set? > > It

Re: Tickets: Milestone vs. Version

On Sat, Aug 11, 2018 at 5:14 AM, Chris Johns wrote: > On 11/8/18 6:31 am, Gedare Bloom wrote: >> On Fri, Aug 10, 2018 at 2:10 AM, Chris Johns wrote: >>> On 10/08/2018 15:41, Sebastian Huber wrote: On 10/08/18 07:38, Chris Johns wrote: > On 10/08/2018 15:03, Sebastian Huber wrote: >>

Re: covoar SIGKILL Investigation

On Tue, Aug 21, 2018, 4:05 PM Vijay Kumar Banerjee wrote: > > On Wed, 22 Aug 2018 at 01:55, Joel Sherrill wrote: > >> >> >> On Tue, Aug 21, 2018, 1:59 PM Vijay Kumar Banerjee < >> vijaykumar9...@gmail.com> wrote: >> >>> >>> >>> On Tue, Aug 21, 2018, 7:34 PM Joel Sherrill wrote: >>>

Re: covoar SIGKILL Investigation

On Wed, 22 Aug 2018 at 01:55, Joel Sherrill wrote: > > > On Tue, Aug 21, 2018, 1:59 PM Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> >> >> On Tue, Aug 21, 2018, 7:34 PM Joel Sherrill wrote: >> >>> >>> >>> On Tue, Aug 21, 2018 at 2:14 AM, Chris Johns wrote: >>> On

Re: covoar SIGKILL Investigation

On Tue, Aug 21, 2018, 1:59 PM Vijay Kumar Banerjee wrote: > > > On Tue, Aug 21, 2018, 7:34 PM Joel Sherrill wrote: > >> >> >> On Tue, Aug 21, 2018 at 2:14 AM, Chris Johns wrote: >> >>> On 21/08/2018 16:55, Vijay Kumar Banerjee wrote: >>> > I tried running coverage with this latest >>> >

Re: covoar SIGKILL Investigation

On Tue, Aug 21, 2018, 7:34 PM Joel Sherrill wrote: > > > On Tue, Aug 21, 2018 at 2:14 AM, Chris Johns wrote: > >> On 21/08/2018 16:55, Vijay Kumar Banerjee wrote: >> > I tried running coverage with this latest >> > master, covoar is taking up all the memory (7 GB) including the swap >> (7.6 GB)

bsp-builder Mystery Failures

Hi Ignoring the epiphany failures (it shouldn't even attempt to build networking but I can't seem to find the .ini syntax to address that), the following results https://lists.rtems.org/pipermail/build/2018-August/000903.html have some failures I don't seem to be able to reproduce by hand. For

Re: covoar SIGKILL Investigation

On Tue, Aug 21, 2018 at 2:14 AM, Chris Johns wrote: > On 21/08/2018 16:55, Vijay Kumar Banerjee wrote: > > I tried running coverage with this latest > > master, covoar is taking up all the memory (7 GB) including the swap > (7.6 GB) > > and after a while, still gets killed. :( > > I ran

Re: covoar SIGKILL Investigation

On 21/08/2018 16:55, Vijay Kumar Banerjee wrote: > I tried running coverage with this latest  > master, covoar is taking up all the memory (7 GB) including the swap (7.6 GB)  > and after a while, still gets killed. :( I ran rtems-test and created the .cov files and then ran covoar from the

Re: covoar SIGKILL Investigation

I tried running coverage with this latest master, covoar is taking up all the memory (7 GB) including the swap (7.6 GB) and after a while, still gets killed. :( can there be something wrong with my environment? I tried running it on a different system, coverage did run for the whole testsuite for