Hello, thanks for your work to make numpy a better package :) On Fri, Dec 14, 2012 at 7:30 PM, Yaroslav Halchenko <deb...@onerussian.com> wrote: > Actually here are two patches (ready to be committed to SVN happen the > maintainer approves) > > - one assures that all for loops are secured with set -e, so if any > command fails, the loop fails (do not remember who pointed me to this drawback > in my packages originally, thanks again ;) )
that makes sense, applied (in my local checkout, will commit once the test build has finished). > - tests failures are not ignored they are * temporarily* ignored. > imho it is much better to submit packages with only known to fail tests > disabled/excluded or > even better resolved that's currently what's being done, cfr https://github.com/numpy/numpy/issues/created_by/sandrotosi?page=1&sort=updated&state=open + closed. > yes -- currently it would lead to FTBFS since all (or nearly all -- that > is the point, impossible to figure out besides going through all of them 1 by > 1) architectures show some kind of test failure or a crash: yes, I know, and as you probably know too, this patch won't be accepted until all those tests are ironed out. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
