[llvm-dev] RFC: LNT/Test-suite support for custom metrics and test parameterization

Wed May 25 03:55:00 PDT 2016

Hi James,

Thank you. We use last one, but I don’t know about this option, because I found no information about this in documentation. It may be very useful to add more information about modes of running tests in documentation.
Now I saw source code for test-suite mode.

Thanks,
Elena.

From: James Molloy [mailto:james at jamesmolloy.co.uk]
Sent: Wednesday, May 25, 2016 1:43 PM
To: Elena Lepilkina <Elena.Lepilkina at synopsys.com>; Matthias Braun <matze at braunis.de>
Cc: llvm-dev <llvm-dev at lists.llvm.org>; nd <nd at arm.com>
Subject: Re: [llvm-dev] RFC: LNT/Test-suite support for custom metrics and test parameterization

Hi Elena,

> First of all, now LNT uses make-style of running tests and parse results from result csv file. Are there any plans to go to cmake?

There are two test drivers in LNT. "lnt runtests nt" uses the old Makefile-based system and "lnt runtests test-suite" uses the new cmake-based system. It sounds like you are using the former and should switch to the latter.

Cheers,

James

On Wed, 25 May 2016 at 10:04 Elena Lepilkina via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
Hi Matthias,

Thank you for your answer.
But can you answer for some more questions?
First of all, now LNT uses make-style of running tests and parse results from result csv file. Are there any plans to go to cmake?
As I understood lit will run and collect all metrics, but there is no opportunity to make any settings for choosing what metrics I would like to collect. Test reports files allow to choose what report I would like. One time I can use one, second time I can use another. I can do this with cmake only by changing test_modules in file.
So I can’t group some metrics and give them some name.

Am I right?

Thanks,
Elena.

From: Matthias Braun [mailto:matze at braunis.de<mailto:matze at braunis.de>]
Sent: Friday, May 20, 2016 8:03 PM
To: Elena Lepilkina <Elena.Lepilkina at synopsys.com<mailto:Elena.Lepilkina at synopsys.com>>
Cc: Daniel Dunbar <daniel at zuster.org<mailto:daniel at zuster.org>>; llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>; nd <nd at arm.com<mailto:nd at arm.com>>

Subject: Re: [llvm-dev] RFC: LNT/Test-suite support for custom metrics and test parameterization

On May 12, 2016, at 11:21 PM, Elena Lepilkina via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:

Hi all,

As we understood great changes will be done in LNT, so we are waiting to new LNT version and stopped our work in LNT.

One more question about using test-suite separately with cmake. Cmake can only build all tests and generate lit tests. After that we can run LIT and get report which is not equal with report (simple) got with make. Cmake test-suite version has no features to run custom metrics and generate other report type, right?

Are these features of make-version of test-suite planned to be added?
The lit test-suite runner supports arbitrary metrics, it already features codesizes for different segments, compiletime, linktime, executable hash, execution time. I designed it be easily extensible with further metrics. Not all of these metrics are understood by LNT yet so they may get lost after submission to an LNT database.

We do not use GenerateReport.pl and friends in the cmake/lit version anymore, as the main data collection and reporting mechanism in llvm has mostly shifted to LNT these days. In any case it should be easy to use “lit -o result.json” and process the resulting json file in your favorite scripting language to generate arbitrary reports.

As far as the TEST.*.Makefile things go: Many of those variants have no equivalent in cmake/lit. But I have the strong feeling that the majority of those is not really used or even broken so there are no plans to adding them to. On the other hand I would love to hear from people that actually use any of those besides TEST.simple.Makefile, it should be possible to transition most of them but I’d first like to  hear what they are used for.

- Matthias

_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160525/cd624627/attachment.html>