Open fabaff opened 1 year ago
The problem seems to be that the failure_message
variable isn't being prefixed with the exception classname.
One of the failing tests looks for a pattern *ExpectedMessage: "other message" not in "the message"
-- but what appears (as shown in your output sample) is only the "other message" not in "the message"
part.
The exception classname prefix is added in one of two places, within the same method: either here or here.
I guess that means that the code has begun following this path instead in the affected tests.. but I'm not sure why that is yet.
NB: also, some of the excinfo
output warnings appear to be related to the removal of the _Result._excinfo
attribute in pluggy
v1.1.0 onwards.
In NixOS we get some test failures. It happens on Python 3.10 too. At first glances I would say it's
pytest
-related.