-
Notifications
You must be signed in to change notification settings - Fork 919
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
Pytest uncaught error when integration tests fail #14316
Comments
Another similar stack trace when headless tests failed on prod https://github.com/mozilla/bedrock/actions/runs/8263588521/job/22605363232 |
I saw this on my Django 4.2 branch but not on Python 3.11, so I guess it's somewhat random. I added a commit to my Django 4.2 branch that seemed to fix it: The problem is pytest-selenium attempts to get the value of the This is odd to me since the default value of this setting is the empty string. So my thought was by setting any value to it, we avoid it randomly coming back as a |
Ah, this is a recent change that isn't published yet: In the last Python updates I upgraded pytest. I believe the fix is to downgrade it to what we had before. It seems pytest-selenium won't work on pytest>=8 without the above fix. I'll submit a PR. |
Fixed. d20403c |
Description
When an integration test fails on stage, we're seeing a bunch of uncaught errors instead of the test failure report: https://github.com/mozilla/bedrock/actions/runs/8262326915/job/22601432494
Possibly related to the Python 3.11 update?
The text was updated successfully, but these errors were encountered: