"I've now done that, so I think at this point it's waiting for SRU team
to unblock proposed migration."
This bug is really serious and it's not possible to work around it. I
don't understand why Canonical doesn't care of this major Python crash!?
--
You received this bug notification because
ping?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1367907
Title:
Segfault in gc with cyclic trash
Status in oslo.messaging:
Invalid
Status in Python:
Fix
ping?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1367907
Title:
Segfault in gc with cyclic trash
Status in oslo.messaging:
Invalid
Status in Python:
Fix
The version with the fix in trusty-proposed since 2 months, it was
validated by 2 developers 1 month 1/2 ago, but then nothing happened.
What's going on with this issue?
The fix was pushed into CPython 3.4 on May 2014. Come on Ubuntu, please
do something for Python 3.4! This bug is a major bug. I
I tested on a fresh Ubuntu Trusty (python3.4 package version
3.4.0-2ubuntu1.1): python3 segfaulter.py does crash, where
segfaulter.py comes from http://bugs.python.org/issue21435#msg217918
I upgraded python3.4 package to 3.4.3-1ubuntu1~14.04.1 using deb
http://archive.ubuntu.com/ubuntu/
This issue is still biting us on the OpenStack CI. The py34 test job of
the Oslo Messaging project is crashing randomly, even after disabling
the test using trollius (the bug was initially found on an asyncio
example, and trollius code is very close to asyncio).
Please fix it, Trusty is a LTS
6 matches
Mail list logo
