250 unit test failures under Python 3.11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
In Progress
|
High
|
Eric Harney |
Bug Description
Trying to build Cinder 21.0.0 (Zed) under Python 3.11 in Debian unstable results in 250 unit test failures the way I cut/past below.
This looks like a miss-use of the mock object that now fails. See the doc from upstream Python:
bpo-43478: Mocks can no longer be provided as the specs for other Mocks. As a result, an already-mocked object cannot be passed to mock.Mock(). This can uncover bugs in tests since these Mock-derived Mocks will always pass certain tests (e.g. isinstance) and builtin assert functions (e.g. assert_
python/
https:/
Please help me fix this so that Cinder can stay in Debian and be part of Debian 12 (Bookworm).
FAIL: cinder.
cinder.
-------
testtools.
2022-12-25 17:15:37,860 INFO [keystonemiddle
2022-12-25 17:15:37,867 WARNING [keystonemiddle
2022-12-25 17:15:37,867 WARNING [keystonemiddle
2022-12-25 17:15:37,872 WARNING [keystonemiddle
}}}
Traceback (most recent call last):
File "/usr/lib/
return func(*newargs, **newkeywargs)
File "/<<PKGBUILDDIR
self.
File "/usr/lib/
with self.decoration
File "/usr/lib/
return next(self.gen)
File "/usr/lib/
arg = exit_stack.
File "/usr/lib/
result = _enter(cm)
File "/usr/lib/
new = Klass(**_kwargs)
File "/usr/lib/
_safe_
File "/usr/lib/
_safe_
File "/usr/lib/
self.
File "/usr/lib/
raise InvalidSpecErro
unittest.
Changed in cinder: | |
status: | New → Triaged |
Changed in cinder: | |
status: | Triaged → In Progress |
assignee: | nobody → Eric Harney (eharney) |
Hi Thomas Goirand, hope this message finds you well.
I'll bring this up on the cinder bug meeting. Would you mind sharing the full list of 250 unit test that are failing so i can reproduce in my env?
Thanks in advance,
Sofia