Hi Sandro, On 30.12.2016 15:01, Sandro Tosi wrote: > On Fri, Dec 23, 2016 at 9:47 AM, Ole Streicher <ole.streic...@gmx.de> wrote: >> This is a regression; it did not happen with 1.11. Please fix this >> regression ASAP so that skimage can migrate safely before the freeze. > > as asked on the github issue, is disabling parallel tests execution in > skimage a viable temporary solution?
For the moment, I disabled the build time tests in skimage completely because of #849196, to ensure it migrates before the freeze (I took the really latest chance to do so). Therefore, I would not touch the package before Jan 5. Once it is in testing, It would be however very important to re-enable the tests, since this is more a crude hack than a clean solution. Unfortunately, I am not familar with the skimage code (I just did the firefighter job here); specifically I don't know where to switch off parallel tests, and what other implications that has. Maybe, you discuss this with Yaroslav (in Cc), who is the skimage package maintainer? Also the parallel bug I opened on the "scikit-image" github (referenced on the numpy issue) may help there. Finally, Yaroslav should decide here. I personally however would much more prefer to go back to the latest numpy 1.11 in testing, and update only after 1.12 is released. I very dislike having workarounds because a beta or a release candidate uploaded to testing is buggy. And I would also prefer not to have a beta or RC shipped with Stretch. Best regards Ole
