Skip to content
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

Move up to Fedora 34 defaults #342

Closed
2 tasks done
mulkieran opened this issue Aug 22, 2021 · 3 comments
Closed
2 tasks done

Move up to Fedora 34 defaults #342

mulkieran opened this issue Aug 22, 2021 · 3 comments
Assignees

Comments

@mulkieran
Copy link
Member

mulkieran commented Aug 22, 2021

  • Fix all Fedora 34 test failures:
For each repo with a weekly.yml file:
  * Run it by hand. If all the tests pass, there's nothing to do.
  * Otherwise, make a PR to fix the tests on a Fedora 34 machine

Special note: allow all pylint consider-using-with lints; ones that could be fixed already have been.

  • Bump Jenkins environments to Fedora 34
@mulkieran
Copy link
Member Author

mulkieran commented Aug 23, 2021

There is sort of an already related issue: pylint-dev/pylint#4808. I'll take a look and see if it is related to our cases. EDIT: It is exactly the same. We should mark any remaining consider-using-with lints as false positives.

@mulkieran mulkieran moved this from To do to In progress (long term) in 2021August Aug 23, 2021
@mulkieran mulkieran removed this from In progress (long term) in 2021August Aug 23, 2021
@mulkieran mulkieran added this to To do in 2021September via automation Aug 23, 2021
@mulkieran mulkieran moved this from To do to In progress (long term) in 2021September Aug 23, 2021
@mulkieran mulkieran changed the title Fix future Fedora pylint errors wherever possible Move up to Fedora 34 defaults Aug 26, 2021
@mulkieran mulkieran assigned bgurney-rh and unassigned mulkieran Sep 1, 2021
@mulkieran mulkieran moved this from In progress (long term) to In progress in 2021September Sep 3, 2021
@mulkieran
Copy link
Member Author

@bgurney-rh Plz bump Jenkins machines and then we can close this issue.

@mulkieran
Copy link
Member Author

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants