-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Run and upload primer over packages #6714
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
Conversation
Pull Request Test Coverage Report for Build 2397704965
π - Coveralls |
arguments += [f"--rcfile={data.pylintrc_relpath}"] | ||
output = StringIO() | ||
reporter = JSONReporter(output) | ||
Run(arguments, reporter=reporter, do_exit=False) |
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 don't want to lint every primer package twice, so I think we will need to turn off the python test that checks for crashes, yeah?
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.
Yes! Although this still needs some work before we get there. We don't actually prime on astroid
and black
doesn't take too long. So for now I think this is fine.
Co-authored-by: Jacob Walls <[email protected]>
for more information, see https://pre-commit.ci
Should we bump
|
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.
LGTM,, but I think @jacobtylerwalls is right that we should try to remove the package from the normal primer if they are in the false positive primer.
@@ -26,14 +26,16 @@ jobs: | |||
steps: | |||
- name: Check out code from GitHub | |||
uses: actions/[email protected] | |||
with: | |||
fetch-depth: 0 |
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 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 think it's unlikely we'll forget to turn off the double-primer runs once we enable running this over the full set of primer repositories, so if you wish to merge now and then sort that out in a future PR, ππ»
Type of Changes
Description
Ref. #5364.
Next step for the primer.
Test run on local
main
:https://github.com/DanielNoord/pylint/actions/runs/2396609324
Test run on a PR:
https://github.com/DanielNoord/pylint/actions/runs/2396610764
Basically, the PR run will now result in three files: the PR number, the output of the primer on the PR and the output of the
main
run against which the PR is being compared.This can be downloaded by a last and final step which takes all these files. Compares them and then comments on the relevant PR.