Chris Matthews via llvm-dev
2015-Sep-21 23:27 UTC
[llvm-dev] [RFC] LNT Feature: tracking performance changes
I agree. I plan to implement that next!> On Sep 21, 2015, at 4:25 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > However, I think that unless we're able to e-mail commit authors who cause regressions like we do for buildbot failures, as well as others who are architecture performance experts on the relevant systems, this won't see the use it needs.-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150921/6d44b09e/attachment.html>
David Blaikie via llvm-dev
2015-Sep-22 05:01 UTC
[llvm-dev] [RFC] LNT Feature: tracking performance changes
Usual caveats apply: timely, narrow-blame, low false positive, and ideally reproducible (cheaply/easily). Or the emails/issues won't be actionable/actioned. On Mon, Sep 21, 2015 at 4:27 PM, Chris Matthews via llvm-dev < llvm-dev at lists.llvm.org> wrote:> I agree. I plan to implement that next! > > On Sep 21, 2015, at 4:25 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > However, I think that unless we're able to e-mail commit authors who > cause regressions like we do for buildbot failures, as well as others who > are architecture performance experts on the relevant systems, this won't > see the use it needs. > > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150921/4ba91eb1/attachment-0001.html>
Chris Matthews via llvm-dev
2015-Sep-22 16:49 UTC
[llvm-dev] [RFC] LNT Feature: tracking performance changes
Yes. I will send out a proposal to the list about how to do that when the time comes.> On Sep 21, 2015, at 10:01 PM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Usual caveats apply: timely, narrow-blame, low false positive, and ideally reproducible (cheaply/easily). Or the emails/issues won't be actionable/actioned. > > On Mon, Sep 21, 2015 at 4:27 PM, Chris Matthews via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > I agree. I plan to implement that next! > >> On Sep 21, 2015, at 4:25 PM, Hal Finkel <hfinkel at anl.gov <mailto:hfinkel at anl.gov>> wrote: >> >> However, I think that unless we're able to e-mail commit authors who cause regressions like we do for buildbot failures, as well as others who are architecture performance experts on the relevant systems, this won't see the use it needs. > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev> > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150922/3732a7bb/attachment.html>