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

1631: Pin black, moto, pytest versions to avoid breaking changes to tests #1632

Conversation

richardt-engineb
Copy link
Contributor

Summary

Over the weekend (26-27 Jan 2024) there were major updates to black, moto, and pytest that broke the tests. This commit pins the versions of those tools to before their major updates to get the automated running & passing again.

Actual updates to the code to be in line with the latest versions can follow in a later PR.

Tests

Run hatch -e ci.py3.10 run test and ensure all tests run and pass (with test db images up and running).

…ests

# Summary

Over the weekend (26-27 Jan 2024) there were major updates to black, moto, and pytest that broke the tests.  This commit pins the versions of those tools to before their major updates to get the automated running & passing again.

Actual updates to the code to be in line with the latest versions can follow in a later PR.

# Tests

Run `hatch -e ci.py3.10 run test` and ensure all tests run and pass (with test db images up and running).
@richardt-engineb richardt-engineb force-pushed the 1631-fix-automated-tests branch from 0f828ad to 96da320 Compare January 30, 2024 14:48
@barbuz barbuz mentioned this pull request Feb 16, 2024
@roll
Copy link
Member

roll commented Apr 29, 2024

Thanks! Fixed by #1652

@roll roll closed this Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automated tests failing in main
2 participants