This is an archive of the discontinued LLVM Phabricator instance.

[LNT] Generate csv test report for test-suite
ClosedPublic

Authored by kristof.beyls on Jan 11 2017, 6:44 AM.

Details

Summary

csv test reports are typically easier to quickly analyze than json or
xml reports. Therefore, also create a csv test report as part of 'lnt
runtest test-suite'; similar to how it's done for 'lnt runtest nt'.

Hopefully this is one of many steps to still take to be able to
deprecate 'lnt runtest nt'.

Diff Detail

Repository
rL LLVM

Event Timeline

kristof.beyls retitled this revision from to [LNT] Generate csv test report for test-suite.
kristof.beyls updated this object.
kristof.beyls added reviewers: cmatthews, MatzeB.
kristof.beyls added a subscriber: llvm-commits.

Correct test name generation for CSV output.

MatzeB accepted this revision.Jan 11 2017, 9:42 AM
MatzeB edited edge metadata.

IMO lnt runtest should rather be lnt submit and not drive the whole build and run, but that discussion is for another day :)

That said with things as they are this LGTM. You may want to wait a bit if Chris has comments as he is probably a better reviewer for LNT code.

This revision is now accepted and ready to land.Jan 11 2017, 9:42 AM
cmatthews added inline comments.Jan 11 2017, 10:41 AM
lnt/tests/test_suite.py
74 ↗(On Diff #83977)

I have never seen the {%- syntax in Jinja2, are you using {%- over the standard {% for some reason?

MatzeB added inline comments.Jan 11 2017, 10:55 AM
lnt/tests/test_suite.py
74 ↗(On Diff #83977)

That syntax removes the whitespace before the {% from what I remember :)

cmatthews accepted this revision.Jan 11 2017, 11:20 AM
cmatthews edited edge metadata.

Ah, I see. LGTM!

That syntax removes the whitespace before the {% from what I remember :)

Indeed, see http://jinja.pocoo.org/docs/2.9/templates/#whitespace-control for the details.
It's necessary in this case since the white space matters in a csv file.

This revision was automatically updated to reflect the committed changes.