Latest upstream release: 6.0.0rc1 Current version/release in rawhide: 5.7.8-1.fc31 URL: https://jupyter.org/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/10529/
Created attachment 1585023 [details] [patch] Update to 6.0.0rc1 (#1724407)
Latest upstream release: 6.0.0 Current version/release in rawhide: 5.7.8-2.fc31 URL: https://jupyter.org/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/10529/
Created attachment 1604567 [details] [patch] Update to 6.0.0 (#1724407)
Latest upstream release: 6.0.1 Current version/release in rawhide: 5.7.8-3.fc32 URL: https://jupyter.org/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/10529/
Created attachment 1606821 [details] [patch] Update to 6.0.1 (#1724407)
the-new-hotness/release-monitoring.org's scratch build of python-notebook-6.0.1-1.fc29.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=37215076
FAILED (SKIP=1, errors=20, failures=1) Resource temporarily unavailable (src/ctx.cpp:184) Resource temporarily unavailable (src/ctx.cpp:184) Assertion failed: pfd.revents & POLLIN (src/signaler.cpp:264) #0 0xfefc66031a10 in ? (?+0x7f7e327c0780) #1 0xfefc66024a60 in ? (?+0x7f7e327c0780) #2 0x7f7e338b9c6e in /lib64/libzmq.so.5 (zmq_ctx_term+0x2e) #3 0x7f7e332f5e04 in /usr/lib64/python3.8/site-packages/zmq/backend/cython/context.cpython-38-x86_64-linux-gnu.so (PyInit_context+0x7194) #4 0x7f7e338eca90 in /usr/lib64/python3.8/site-packages/zmq/backend/cython/error.cpython-38-x86_64-linux-gnu.so (PyInit_error+0x12f0) #5 0x7f7e353e8c40 in /lib64/libpython3.8.so.1.0 (_PyObject_MakeTpCall+0x230) #6 0x7f7e353a7635 in /lib64/libpython3.8.so.1.0 (PyUnicode_AsCharmapString+0x9d4) #7 0x7f7e354495b9 in /lib64/libpython3.8.so.1.0 (_PyEval_EvalFrameDefault+0x50e9) #8 0x7f7e353e9ee1 in /lib64/libpython3.8.so.1.0 (_PyEval_EvalCodeWithName+0x2f1) #9 0x7f7e35417820 in /lib64/libpython3.8.so.1.0 (_PyFunction_Vectorcall+0x190) #10 0x7f7e353ede10 in /lib64/libpython3.8.so.1.0 (PyVectorcall_Call+0x70) #11 0x7f7e35446aba in /lib64/libpython3.8.so.1.0 (_PyEval_EvalFrameDefault+0x25ea) #12 0x7f7e3541778a in /lib64/libpython3.8.so.1.0 (_PyFunction_Vectorcall+0xfa) #13 0x7f7e35444c90 in /lib64/libpython3.8.so.1.0 (_PyEval_EvalFrameDefault+0x7c0) #14 0x7f7e3541778a in /lib64/libpython3.8.so.1.0 (_PyFunction_Vectorcall+0xfa) #15 0x7f7e35444c90 in /lib64/libpython3.8.so.1.0 (_PyEval_EvalFrameDefault+0x7c0) #16 0x7f7e3541778a in /lib64/libpython3.8.so.1.0 (_PyFunction_Vectorcall+0xfa) #17 0x7f7e35434566 in /lib64/libpython3.8.so.1.0 (PyUnicode_Format+0x1ce6) #18 0x7f7e353ede10 in /lib64/libpython3.8.so.1.0 (PyVectorcall_Call+0x70) #19 0x7f7e354df17a in /lib64/libpython3.8.so.1.0 (PyImport_Cleanup+0x41a) #20 0x7f7e35458094 in /lib64/libpython3.8.so.1.0 (PyOS_mystrnicmp+0x1674) #21 0x7f7e352af4e2 in /lib64/libpthread.so.0 (start_thread+0xe2) #22 0x7f7e3572c300 in /lib64/libc.so.6 (clone+0x43) /var/tmp/rpm-tmp.Otq2ox: line 36: 3416 Aborted (core dumped) nosetests-3 -v --exclude-dir notebook/tests/selenium Is this a Vectorcall regression or some other kind of problem? Petr, Victor? Reproducer at https://src.fedoraproject.org/rpms/python-notebook/pull-request/15
The reproduces shows different failures: https://kojipkgs.fedoraproject.org//work/tasks/8283/37308283/build.log This doesn't look like a vectorcall issue.
With more debug info installed, I get a different error. It looks like ØMQ fails hard with "Resource temporarily unavailable" when one of 9 threads is destroying a context: Backtrace with some more debug info (and my comments): #0 0x00007ffff7e3a615 in raise () from /lib64/libc.so.6 #1 0x00007ffff7e238d9 in abort () from /lib64/libc.so.6 #2 0x00007ffff60422a4 in zmq::zmq_abort (errmsg_=errmsg_@entry=0x7ffff7f8f260 "Resource temporarily unavailable") #3 0x00007ffff603574a in zmq::ctx_t::terminate (this=this@entry=0x7ffff050d8b0) at src/ctx.cpp:184 #4 0x00007ffff608ac6e in zmq_ctx_term (ctx_=0x7ffff050d8b0) at src/zmq.cpp:156 #5 0x00007ffff5abfd8f in __pyx_f_3zmq_7backend_6cython_7context_7Context__term (__pyx_v_self=0x7fffef8e14a0) probably from "zmq/backend/cython/context.pyx":121: rc = zmq_ctx_destroy(self.handle) #6 __pyx_pf_3zmq_7backend_6cython_7context_7Context_6term (__pyx_v_self=0x7fffef8e14a0) from "zmq/backend/cython/context.pyx":134: rc = self._term() #7 __pyx_pw_3zmq_7backend_6cython_7context_7Context_7term ( __pyx_v_self=<Context(_shadow=False, sockopts={}) at remote 0x7fffef8e14a0>, unused=<optimized out>) #8 0x00007ffff60bc819 in __Pyx_CyFunction_CallAsMethod (kw=0x0, args=(<Context(_shadow=False, sockopts={}) at remote 0x7fffef8e14a0>,), func=<cython_function_or_method at remote 0x7ffff614cb80>) at zmq/backend/cython/error.c:2339 #9 __Pyx_CyFunction_CallAsMethod (func=<cython_function_or_method at remote 0x7ffff614cb80>, args=(<Context(_shadow=False, sockopts={}) at remote 0x7fffef8e14a0>,), kw=0x0) at zmq/backend/cython/error.c:2323 #10 0x00007ffff7bbbc40 in _PyObject_MakeTpCall (callable=<cython_function_or_method at remote 0x7ffff614cb80>, args=<optimized out>, nargs=<optimized out>, keywords=<optimized out>) at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Objects/call.c:168 #11 0x00007ffff7b79cb8 in _PyObject_Vectorcall (kwnames=0x0, nargsf=<optimized out>, args=0x7ffff03ca560, callable=<cython_function_or_method at remote 0x7ffff614cb80>) at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Include/cpython/abstract.h:125 #12 _PyObject_Vectorcall (kwnames=0x0, nargsf=<optimized out>, args=0x7ffff03ca560, callable=<cython_function_or_method at remote 0x7ffff614cb80>) #13 method_vectorcall (method=<optimized out>, args=0x7ffff03ca568, nargsf=<optimized out>, kwnames=0x0) #14 0x00007ffff7c1c5b9 in _PyObject_Vectorcall (kwnames=0x0, nargsf=<optimized out>, args=0x7ffff03ca568, callable=<method at remote 0x7fffec7528c0>) #15 call_function (kwnames=0x0, oparg=<optimized out>, pp_stack=<synthetic pointer>, tstate=0x555556550250) #16 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>) Python function: NotebookTestBase.teardown_class.<locals>.cleanup_zmq (and more frames for Python threading._bootstrap / threading.run)
The other threads are interesting. In my case: (gdb) info thread Id Target Id Frame 1 Thread 0x7ffff7922740 (LWP 259) "python3" 0x00007ffff7c2bbff in _Py_DECREF (filename=<synthetic pointer>, lineno=541, op='A context manager used to implement TestCase.assertRaises* methods.') at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Include/object.h:541 20 Thread 0x7ffff5035700 (LWP 388) "python3" 0x00007ffff7ef47bf in poll () from /lib64/libc.so.6 22 Thread 0x7fffedfcb700 (LWP 391) "python3" 0x00007ffff7ef47bf in poll () from /lib64/libc.so.6 24 Thread 0x7fffed7ca700 (LWP 394) "python3" 0x00007ffff7ef47bf in poll () from /lib64/libc.so.6 26 Thread 0x7fffecf89700 (LWP 397) "python3" 0x00007ffff5fff749 in _Ux86_64_get_elf_image () * 28 Thread 0x7fffd7fff700 (LWP 431) "python3" 0x00007ffff7e3a615 in raise () from /lib64/libc.so.6 30 Thread 0x7fffd77fe700 (LWP 436) "python3" 0x00007ffff7ef47bf in poll () from /lib64/libc.so.6 34 Thread 0x7fffd67fc700 (LWP 442) "python3" 0x00007ffff7ef47bf in poll () from /lib64/libc.so.6 36 Thread 0x7fffd5ffb700 (LWP 450) "python3" 0x00007ffff7a8c600 in __lll_lock_wait () from /lib64/libpthread.so.0 thread 28 is crashing as above thread 26 is crashing in a similar way (zmq_abort): #0 0x00007ffff5fff749 in _Ux86_64_get_elf_image () from /lib64/libunwind.so.8 #1 0x00007ffff60076cb in _Uelf64_get_proc_name () from /lib64/libunwind.so.8 #2 0x00007ffff60005f0 in _ULx86_64_get_proc_name () from /lib64/libunwind.so.8 #3 0x00007ffff60420b3 in zmq::print_backtrace () at src/err.cpp:423 #4 0x00007ffff604229f in zmq::zmq_abort (errmsg_=errmsg_@entry=0x7ffff7f8f260 "Resource temporarily unavailable") at src/err.cpp:87 #5 0x00007ffff603574a in zmq::ctx_t::terminate (this=this@entry=0x7ffff050d8b0) at src/ctx.cpp:184 ... Thread 1 is cleaning up the interpreter (here, garbage-collecting the docstring of unittest.case._AssertRaisesContext): #0 0x00007ffff7c2bbff in _Py_DECREF (filename=<synthetic pointer>, lineno=541, op='A context manager used to implement TestCase.assertRaises* methods.') at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Include/object.h:541 #1 _Py_XDECREF (op='A context manager used to implement TestCase.assertRaises* methods.') at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Include/object.h:541 #2 free_keys_object (keys=0x7ffff6fa9d40) at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Objects/dictobject.c:580 #3 0x00007ffff7c2d3e6 in type_clear (type=0x5555556e81b0) at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Objects/typeobject.c:3595 #4 0x00007ffff7bb25d4 in delete_garbage (state=<optimized out>, state=<optimized out>, old=<optimized out>, collectable=<optimized out>) at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Modules/gcmodule.c:929 #5 collect (generation=2, n_collected=0x0, n_uncollectable=0x0, nofail=1, state=0x7ffff7ddd758 <_PyRuntime+344>) at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Modules/gcmodule.c:1095 #6 0x00007ffff7cb1982 in _PyGC_CollectNoFail () at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Modules/gcmodule.c:1843 #7 0x00007ffff7cb1d0d in PyImport_Cleanup () at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Python/import.c:598 #8 0x00007ffff7cb2016 in Py_FinalizeEx () at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Python/pylifecycle.c:1226 #9 0x00007ffff7cb3254 in Py_RunMain () at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Modules/main.c:648 #10 0x00007ffff7cb3619 in Py_BytesMain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/python3-3.8.0~b3-4.fc32.x86_64/Modules/main.c:700 #11 0x00007ffff7e25193 in __libc_start_main () from /lib64/libc.so.6 #12 0x000055555555508e in _start ()
This is very suspicious: Thread 26: #6 0x00007ffff608ac6e in zmq_ctx_term (ctx_=0x7ffff050d8b0) at src/zmq.cpp:156 Thread 28: #4 0x00007ffff608ac6e in zmq_ctx_term (ctx_=0x7ffff050d8b0) at src/zmq.cpp:156 Two threads are attempting to destroy the same ØMQ context at the same time. I don't think I can make much more progress in debugging this. I'm not all that familiar with ØMQ. It might be better to focus on the test failures (RuntimeError: Failed to teardown zmq Context, open sockets likely left lying around.) rather than the C crash at shutdown.
Thanks!
Latest upstream release: 6.0.2 Current version/release in rawhide: 5.7.8-4.fc32 URL: https://jupyter.org/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/10529/
Created attachment 1632790 [details] [patch] Update to 6.0.2 (#1724407)
the-new-hotness/release-monitoring.org's scratch build of python-notebook-6.0.2-1.fc29.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=38769465
https://src.fedoraproject.org/rpms/python-notebook/pull-request/15