Skip to content

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

Merged
merged 5 commits into from
May 28, 2022
Merged

Conversation

DanielNoord
Copy link
Collaborator

  • Add yourself to CONTRIBUTORS if you are a new contributor.
  • Write a good description on what the PR does.

Type of Changes

Type
βœ“ πŸ”¨ Refactoring

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.

@coveralls
Copy link

coveralls commented May 27, 2022

Pull Request Test Coverage Report for Build 2397704965

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 15 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.1%) to 95.517%

Files with Coverage Reduction New Missed Lines %
pylint/lint/message_state_handler.py 7 96.55%
pylint/pyreverse/utils.py 8 94.24%
Totals Coverage Status
Change from base Build 2396202454: 0.1%
Covered Lines: 16234
Relevant Lines: 16996

πŸ’› - Coveralls

arguments += [f"--rcfile={data.pylintrc_relpath}"]
output = StringIO()
reporter = JSONReporter(output)
Run(arguments, reporter=reporter, do_exit=False)
Copy link
Member

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?

Copy link
Collaborator Author

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.

@jacobtylerwalls
Copy link
Member

Should we bump setup-node to v3? See:

Warning: Input 'version' has been deprecated with message: The version property will not be supported after October 1, 2019. Use node-version instead

Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas left a 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ‘

Copy link
Member

@jacobtylerwalls jacobtylerwalls left a 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, πŸ‘πŸ»

@DanielNoord DanielNoord merged commit e642066 into pylint-dev:main May 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants