[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [linuxtools-dev] Remote oprofile
|
----- Original Message -----
> From: "Wainer Moschetta" <wainersm@xxxxxxxxxxxxxxxxxx>
> To: linuxtools-dev@xxxxxxxxxxx
> Sent: Tuesday, July 2, 2013 7:04:01 PM
> Subject: Re: [linuxtools-dev] Remote oprofile
>
>
> On 07/02/2013 11:56 AM, Roland Grunberg wrote:
> >> Roland, why wasn't it part of our Kepler contribution?
> >> This needs to be fixed for Kepler SR1. Would you please open a bug report
> >> for
> >> it.?
> >>
> >> Alex
> > I've filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=412114 to keep
> > track
> > of this.
> >
> > Part of the problem may be that when new functionality is added, it's
> > probably
> > not added immediately to our categories/b3aggrcon/cpp-epp locations, and as
> > a
> > result is probably forgotten later on.
> >
> > In the case of the remote profiling functionality, maybe even adding to the
> > manual tests might help.
> >
> > http://wiki.eclipse.org/Linux_Tools_Project/Manual_Testing
> >
> BTW, I've quickly made some sanity test on remote capabilities of perf,
> oprofile and valgrind plug-ins and they all are failing. I didn't have
> time to go back afterwards to double-check I wasn't making any mistake
> but, yes, apparently they stopped working on 2.0.
Let me reiterate myself:
Without proper unit testing verifying functionality doesn't break every release will have such problems. It's just impossible that 2 or 3 people test every single feature manually.
Let's try to get tests added at least when we change something.
Alex
>
> Could someone else test they?
>
> Thanks,
>
> Wainer
>
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
>
