We have a unittest that is decorated with @unittest.skipIf(...), and when green is collecting tests results in stopTest() we get an AttributeError for start_time on this line:
self.test_time = str(time.time() - self.start_time).
Since self.start_time is being set in startTest() but this seems to be skipped on skipped tests, but stopTest() is still being called, it looks like it is a new compatibility issue.
If I silence the AttributeError, we get an other one later on proto_test_result.errors in addProtoTestResult(), so the fix might get tricky.
I will take a look at a permanent fix after 3.5.0 gets released. For new we have commented out the skipped test in our codebase so we can use 3.12.1.
https://docs.python.org/3/whatsnew/changelog.html#python-3-12-1-final
I suspect it might be caused by this change: python/cpython#109725
We have a unittest that is decorated with
@unittest.skipIf(...), and when green is collecting tests results instopTest()we get anAttributeErrorforstart_timeon this line:self.test_time = str(time.time() - self.start_time).Since
self.start_timeis being set instartTest()but this seems to be skipped on skipped tests, butstopTest()is still being called, it looks like it is a new compatibility issue.If I silence the AttributeError, we get an other one later on
proto_test_result.errorsinaddProtoTestResult(), so the fix might get tricky.I will take a look at a permanent fix after 3.5.0 gets released. For new we have commented out the skipped test in our codebase so we can use 3.12.1.
https://docs.python.org/3/whatsnew/changelog.html#python-3-12-1-final
I suspect it might be caused by this change: python/cpython#109725