Your message dated Wed, 19 Feb 2014 17:53:04 +0100 with message-id <1392828784.12680.40.ca...@rama.villemot.name> and subject line Re: Bug#737675: openblas: openmp change deadlocks python-scipy has caused the Debian Bug report #737675, regarding openblas: openmp change deadlocks python-scipy to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 737675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: openblas Version: 0.2.8-3 Severity: important the recent switch of openblas to openmp causes deadlocks in the scipy testsuite: e.g. in sid: apt-get install python-scipy python-nose python -c "import scipy.spatial; scipy.spatial.test('full', verbose=5)" it will deadlock eating all cpu in gomp at the end. This is the typical failure pattern caused by forks combined with gnu openmp (see https://github.com/xianyi/OpenBLAS/issues/294) But the weird part is this testsuite does not fork at all, so it might be a different issue. It did not occur when openblas was still using pthreads. Given the problems openmp based openblas causes in the python world (see the linked issue) I would prefer if the change was reverted or openmp variant split into a separate alternative.
--- End Message ---
--- Begin Message ---Version: 0.2.8-4 Le mardi 04 février 2014 à 22:42 +0100, Julian Taylor a écrit : > Package: openblas > Version: 0.2.8-3 > Severity: important > > the recent switch of openblas to openmp causes deadlocks in the scipy > testsuite: > e.g. in sid: > apt-get install python-scipy python-nose > python -c "import scipy.spatial; scipy.spatial.test('full', verbose=5)" > > it will deadlock eating all cpu in gomp at the end. > This is the typical failure pattern caused by forks combined with gnu > openmp (see https://github.com/xianyi/OpenBLAS/issues/294) > > But the weird part is this testsuite does not fork at all, so it might > be a different issue. > It did not occur when openblas was still using pthreads. > > Given the problems openmp based openblas causes in the python world (see > the linked issue) I would prefer if the change was reverted or openmp > variant split into a separate alternative. Reverted to pthreads. -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594
signature.asc
Description: This is a digitally signed message part
--- End Message ---
-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
