Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-11 Thread Erich Schubert
You can also do this as sponsored upload. On Sun, Mar 12, 2017 at 12:24 AM, Santiago Vila wrote: > On Sat, Mar 11, 2017 at 11:38:44PM +0100, Erich Schubert wrote: > > Hello, > > Could you do a NMU with this version, and ask for a freeze exception, > > please? > > I will gladly make a sponsored u

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-11 Thread Santiago Vila
On Sat, Mar 11, 2017 at 11:38:44PM +0100, Erich Schubert wrote: > Hello, > Could you do a NMU with this version, and ask for a freeze exception, > please? I will gladly make a sponsored upload with the last patch "as is". (NMU would be 0.7.1-2.1 and would have my name on it, but this is not neces

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-11 Thread Erich Schubert
Hello, Could you do a NMU with this version, and ask for a freeze exception, please? There are no dependencies onto elki, so this cannot cause other packages to become broken or uninstallable. Thank you! Erich On Fri, Mar 10, 2017 at 12:07 AM, Santiago Vila wrote: > On Thu, Mar 09, 2017 at 07:09

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-09 Thread Santiago Vila
On Thu, Mar 09, 2017 at 07:09:22PM +0100, Erich Schubert wrote: > Looks good, thank you. > Maybe "Temporarily disable test suite.", as I do want to have it back > eventually; the latest when I prepare a new upstream. Ok, updated patch attached. Notes: If you don't have a sid chroot at hand, you

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-09 Thread Santiago Vila
On Thu, Mar 09, 2017 at 07:12:38PM +0100, Erich Schubert wrote: > Hi, > The CASHTest failure is interesting. Can you share the log? The others are > all time dependent. > CASH could depend on random, but the tests would all try to fix random > seeding. Sure. I've put all my logs (both successful a

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-09 Thread Erich Schubert
Hi, The CASHTest failure is interesting. Can you share the log? The others are all time dependent. CASH could depend on random, but the tests would all try to fix random seeding. On Wed, Mar 8, 2017 at 6:57 PM, Santiago Vila wrote: > On Wed, Mar 08, 2017 at 06:13:34PM +0100, Erich Schubert wrote

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-09 Thread Erich Schubert
Looks good, thank you. Maybe "Temporarily disable test suite.", as I do want to have it back eventually; the latest when I prepare a new upstream. On Thu, Mar 9, 2017 at 5:13 PM, Santiago Vila wrote: > Ok, full patch for your consideration. > > Thanks.

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-09 Thread Santiago Vila
Ok, full patch for your consideration. Thanks.diff -Nru elki-0.7.1/debian/changelog elki-0.7.1/debian/changelog --- elki-0.7.1/debian/changelog 2016-09-25 15:27:58.0 +0200 +++ elki-0.7.1/debian/changelog 2017-03-09 16:57:30.0 +0100 @@ -1,3 +1,10 @@ +elki (0.7.1-3) unstable; urgency

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-09 Thread Erich Schubert
tag 843038 +patch thanks Hello, Either of these two patches will fix this for now and is fine with me. A nicer patch would be to replace all lines matching @Test(timeout with //@Test(timeout to disable only those tests that rely on a timeout (i.e. that will fail on a too slow CPU). These tests a

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-08 Thread Santiago Vila
On Wed, Mar 08, 2017 at 06:13:34PM +0100, Erich Schubert wrote: > Or you just add* e.g. the -*Dmaven.test.skip=true parameter, and it will > build fine. You probably mean the first attached patch. I've tested that and it still run tests (not sure if all of them or only some of them). The second

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-08 Thread Santiago Vila
On Wed, Mar 08, 2017 at 06:13:34PM +0100, Erich Schubert wrote: > Or you just add* e.g. the -*Dmaven.test.skip=true parameter, and it will > build fine. That would be the easy thing, indeed, but not necessarily the right thing to do. This is really a decision to be made by the maintainer: Either

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-08 Thread Erich Schubert
Congratualtions! Go ahead and annoy people. That is exactly the way to build community! --- Or you just add* e.g. the -*Dmaven.test.skip=true parameter, and it will build fine. But apparently you do not care about importance of bugs at all, only about processes and your personal opinion. Heck

Bug#843038: elki: FTBFS randomly (failing tests)

2017-03-07 Thread Santiago Vila
severity 843038 serious thanks Dear maintainer: I expected a general guideline from Release Managers regarding packages which FTBFS randomly like this one, but that will most surely not happen for stretch. So, the only guideline I have left is the one expressed by Julien Cristau (one of the RMs)

Bug#843038: elki: FTBFS randomly (failing tests)

2016-11-03 Thread Santiago Vila
I tried building this package 50 times in different autobuilders (QEMU/KVM machines with a single CPU), using sbuild. This is the result: Status: successful elki_0.7.1-2_amd64-20161103T131214Z Status: failed elki_0.7.1-2_amd64-20161103T131205Z Status: successful elki_0.7.1-2_amd64-20161103