-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misc CI improvements #289
Misc CI improvements #289
Changes from all commits
44c526c
df238c3
448266b
beac9b4
b5ed4c6
8a7c769
30acad1
14d23e6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -104,6 +104,18 @@ known_first_party = 'mesonpy' | |
disable_warnings = [ | ||
'couldnt-parse', | ||
] | ||
source = ['.'] | ||
omit = [ | ||
'tests/packages/*', | ||
] | ||
|
||
[tool.coverage.report] | ||
ignore_errors = true | ||
exclude_lines = [ | ||
'\#\s*pragma: no cover', # we need this because this field overrides the default | ||
'^\s*raise NotImplementedError\b', | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why exclude There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes but |
||
'^\sif typing.TYPE_CHECKING', | ||
] | ||
|
||
[tool.coverage.html] | ||
show_contexts = true | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the point of reporting coverage data to codecov if we don't do anything with it? I would just get rid of the coverage reporting altogether.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do, https://github.com/seantis/pytest-codecov is a plugin to upload the coverage data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know, but where is the data visualized?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://app.codecov.io/gh/mesonbuild/meson-python/ and the badge in the README and docs. I'd like to improve the coverage, so IMO it's definitely useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There must be something wrong with the codevcov.io: it does not point to the source code in this repository. and looking at the details for any given file just shows "There was a problem getting the source code from your provider. Unable to show line by line coverage."
I don't expect that running the code on different flavors of Linux will exercise different code paths, and this doubles the CI execution time. I prefer fast feedback loops. Are we sure we really need this? Does codecov provide a measure of how much each "measurement" from each test run contributes to the total coverage?