<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm-project.git/llvm/utils/prepare-code-coverage-artifact.py, branch users/nico/python-1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/'/>
<entry>
<title>[llvm-cov] Enable `-show-directory-coverage` for LLVM itself.</title>
<updated>2023-08-24T12:26:12+00:00</updated>
<author>
<name>Yuhao Gu</name>
<email>yhgu2000@outlook.com</email>
</author>
<published>2023-08-24T05:04:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=64425caba29e62b42dfa7e03a47a37d9ee9c47aa'/>
<id>64425caba29e62b42dfa7e03a47a37d9ee9c47aa</id>
<content type='text'>
My previous patch D151283 added a new option to llvm-cov to make it generate a hierarchical report for better view. This patch is to enable it for the coverage report of LLVM itself.

Reviewed By: phosek

Differential Revision: https://reviews.llvm.org/D158703
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
My previous patch D151283 added a new option to llvm-cov to make it generate a hierarchical report for better view. This patch is to enable it for the coverage report of LLVM itself.

Reviewed By: phosek

Differential Revision: https://reviews.llvm.org/D158703
</pre>
</div>
</content>
</entry>
<entry>
<title>[NFC][Py Reformat] Reformat python files in llvm</title>
<updated>2023-05-17T08:48:52+00:00</updated>
<author>
<name>Tobias Hieta</name>
<email>tobias@hieta.se</email>
</author>
<published>2023-05-15T09:02:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=b71edfaa4ec3c998aadb35255ce2f60bba2940b0'/>
<id>b71edfaa4ec3c998aadb35255ce2f60bba2940b0</id>
<content type='text'>
This is the first commit in a series that will reformat
all the python files in the LLVM repository.

Reformatting is done with `black`.

See more information here:

https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Reviewed By: jhenderson, JDevlieghere, MatzeB

Differential Revision: https://reviews.llvm.org/D150545
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is the first commit in a series that will reformat
all the python files in the LLVM repository.

Reformatting is done with `black`.

See more information here:

https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Reviewed By: jhenderson, JDevlieghere, MatzeB

Differential Revision: https://reviews.llvm.org/D150545
</pre>
</div>
</content>
</entry>
<entry>
<title>[Utils] Add -compilation-dir flag to prepare-code-coverage-artifact.py</title>
<updated>2021-07-20T17:55:49+00:00</updated>
<author>
<name>Zequan Wu</name>
<email>zequanwu@google.com</email>
</author>
<published>2021-07-19T21:26:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=8773822c578ab76e78a9524ef0ddedfaa4904cd3'/>
<id>8773822c578ab76e78a9524ef0ddedfaa4904cd3</id>
<content type='text'>
Differential Revision: https://reviews.llvm.org/D106314
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Differential Revision: https://reviews.llvm.org/D106314
</pre>
</div>
</content>
</entry>
<entry>
<title>svn propset svn:executable on utils/prepare-code-coverage-artifact.py</title>
<updated>2019-06-04T23:35:07+00:00</updated>
<author>
<name>Nico Weber</name>
<email>nicolasweber@gmx.de</email>
</author>
<published>2019-06-04T23:35:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=577d59bc679d0348ed2f0d6e759fbc728c1f8dbd'/>
<id>577d59bc679d0348ed2f0d6e759fbc728c1f8dbd</id>
<content type='text'>
llvm-svn: 362561
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
llvm-svn: 362561
</pre>
</div>
</content>
</entry>
<entry>
<title>[Coverage] Apply filtered paths to summary</title>
<updated>2018-10-11T04:00:51+00:00</updated>
<author>
<name>Chris Bieneman</name>
<email>chris.bieneman@me.com</email>
</author>
<published>2018-10-11T04:00:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=9a10eac663dd5a2040399a87ae96be76b087c3a6'/>
<id>9a10eac663dd5a2040399a87ae96be76b087c3a6</id>
<content type='text'>
Summary:
The script to generate code coverage reports supports passing filter paths to llvm-cov when generating the HTML reports, but doesn't pass those paths to the summary generation as well. This results in a summary report that doesn't match the HTML report.

This patch addresses the problem by also passing the filter paths to the summary report generation.

Reviewers: vsk

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D53110

llvm-svn: 344217
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary:
The script to generate code coverage reports supports passing filter paths to llvm-cov when generating the HTML reports, but doesn't pass those paths to the summary generation as well. This results in a summary report that doesn't match the HTML report.

This patch addresses the problem by also passing the filter paths to the summary report generation.

Reviewers: vsk

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D53110

llvm-svn: 344217
</pre>
</div>
</content>
</entry>
<entry>
<title>[utils] coverage: Add help text about the --restrict flag (NFC)</title>
<updated>2017-02-09T19:37:18+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2017-02-09T19:37:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=16776315460ed675e7ed403913be6bd4b1aba3f2'/>
<id>16776315460ed675e7ed403913be6bd4b1aba3f2</id>
<content type='text'>
Passing the --restrict flag to the coverage prep script before other
positional arguments is wrong, because it prevents the argparse module
from telling apart arguments to --restrict versus positional arguments.

Pointed out by Sean Callanan!

llvm-svn: 294616
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Passing the --restrict flag to the coverage prep script before other
positional arguments is wrong, because it prevents the argparse module
from telling apart arguments to --restrict versus positional arguments.

Pointed out by Sean Callanan!

llvm-svn: 294616
</pre>
</div>
</content>
</entry>
<entry>
<title>[utils] Add a '--unified-report' option to the code coverage prep script</title>
<updated>2016-10-26T22:07:39+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2016-10-26T22:07:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=f4df0edf3ea39a686abc5753c2d98d61082d02a7'/>
<id>f4df0edf3ea39a686abc5753c2d98d61082d02a7</id>
<content type='text'>
In --unified-report mode, a single coverage report is prepared for all
specified binaries and written to *report_dir*. This mode is compatible
with all existing script options, including the --restrict mode which is
used to limit coverage reporting to certain files or directories.

This should not break any existing users of the script.

llvm-svn: 285249
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In --unified-report mode, a single coverage report is prepared for all
specified binaries and written to *report_dir*. This mode is compatible
with all existing script options, including the --restrict mode which is
used to limit coverage reporting to certain files or directories.

This should not break any existing users of the script.

llvm-svn: 285249
</pre>
</div>
</content>
</entry>
<entry>
<title>[utils] Use print_function in the code coverage prep script, NFC.</title>
<updated>2016-10-26T22:07:37+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2016-10-26T22:07:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=7466987cb7ba5e5de2f02abca5f0e7ae9a608aba'/>
<id>7466987cb7ba5e5de2f02abca5f0e7ae9a608aba</id>
<content type='text'>
llvm-svn: 285248
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
llvm-svn: 285248
</pre>
</div>
</content>
</entry>
<entry>
<title>[utils] Add an '--only-merge' option to the code coverage prep script</title>
<updated>2016-10-26T22:07:35+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2016-10-26T22:07:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=273b6dc3e2f738479efeff2c9050a9648c1dd07e'/>
<id>273b6dc3e2f738479efeff2c9050a9648c1dd07e</id>
<content type='text'>
In --only-merge mode, the script terminates after the profile merging
step.  This makes the script less stateful: it's more natural to split
the merge out into a separate step instead of relying on the first
invocation of the script to do it.

This should not break any existing users of the script.

llvm-svn: 285247
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In --only-merge mode, the script terminates after the profile merging
step.  This makes the script less stateful: it's more natural to split
the merge out into a separate step instead of relying on the first
invocation of the script to do it.

This should not break any existing users of the script.

llvm-svn: 285247
</pre>
</div>
</content>
</entry>
<entry>
<title>[utils] Teach the code coverage prep script about --restrict</title>
<updated>2016-09-22T21:49:49+00:00</updated>
<author>
<name>Vedant Kumar</name>
<email>vsk@apple.com</email>
</author>
<published>2016-09-22T21:49:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=547ebad0b9843b3a5416195fd787281c8e8e7bd3'/>
<id>547ebad0b9843b3a5416195fd787281c8e8e7bd3</id>
<content type='text'>
Add two options to the code coverage artifact prep script:

  * --use-existing-profdata: Use an existing indexed profile instead of
    merging the same profiles again.
  * --restrict: Restrict the coverage reporting to the given list of
    source directories.

With this in place, we can teach the coverage bot how to prepare
separate reports for each of the llvm tools.

llvm-svn: 282204
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add two options to the code coverage artifact prep script:

  * --use-existing-profdata: Use an existing indexed profile instead of
    merging the same profiles again.
  * --restrict: Restrict the coverage reporting to the given list of
    source directories.

With this in place, we can teach the coverage bot how to prepare
separate reports for each of the llvm tools.

llvm-svn: 282204
</pre>
</div>
</content>
</entry>
</feed>
