Bug#888733: hyantesite: test failures on most architectures

2019-05-31 Thread Paul Gevers
Control: retitle -1 should hyantesite be part of buster? Hi, On Tue, 21 May 2019 07:24:17 +0200 Andreas Tille wrote: > On Mon, May 20, 2019 at 08:05:09PM +0100, Rebecca N. Palmer wrote: > > On 19/05/2019 18:15, Andreas Tille wrote: > > > So what is the plan to fix this bug? Create new reference

Bug#888733: hyantesite: test failures on most architectures

2019-05-20 Thread Andreas Tille
On Mon, May 20, 2019 at 08:05:09PM +0100, Rebecca N. Palmer wrote: > On 19/05/2019 18:15, Andreas Tille wrote: > > So what is the plan to fix this bug? Create new references to craft > > a valid test or ignore these tests? > > ...or decide that something that's abandoned and doesn't follow its >

Bug#888733: hyantesite: test failures on most architectures

2019-05-20 Thread Rebecca N. Palmer
On 19/05/2019 18:15, Andreas Tille wrote: So what is the plan to fix this bug? Create new references to craft a valid test or ignore these tests? ...or decide that something that's abandoned and doesn't follow its documentation (even after the above fixes) doesn't belong in Debian stable and

Bug#888733: hyantesite: test failures on most architectures

2019-05-19 Thread Andreas Tille
Hi, On Mon, May 06, 2019 at 09:48:18AM +0100, Rebecca N. Palmer wrote: > It looks like ra_pareto was also broken on amd64 (probably for the same "two > variables with the same name" reason, though I haven't tested this), giving > a constant output within its range circle, and the ra_pareto.out ref

Bug#888733: hyantesite: test failures on most architectures

2019-05-06 Thread Rebecca N. Palmer
It looks like ra_pareto was also broken on amd64 (probably for the same "two variables with the same name" reason, though I haven't tested this), giving a constant output within its range circle, and the ra_pareto.out reference used that broken version (it's identical to ra_disk.out). Hence,

Bug#888733: hyantesite: test failures on most architectures

2019-05-05 Thread Rebecca N. Palmer
However, the "obvious" fix seems to break ra_pareto, for unknown reasons. It's not this change that breaks ra_pareto: it was _already_ totally broken on i386 (all-0s output). Not using the name 'tmp' for two different variables gives some nonzero output: --- a/src/hyantes.c +++ b/src/hyant

Bug#888733: hyantesite: test failures on most architectures

2019-05-05 Thread Rebecca N. Palmer
Control: tags -1 upstream (probably - I haven't actually tried) The missing centre points (0 instead of max at distance=0) are probably due to rounding error in the great circle distance (src/hyantes_run.c:80): equal coordinates should give tmp=acos(1)=0, but rounding error might make it acos(

Bug#888733: hyantesite: test failures on most architectures

2019-05-05 Thread Rebecca N. Palmer
Control: found -1 1.3.0-1.1 Control: retitle -1 hyantesite: test failures on most architectures At least on i386, this *isn't* just -0 vs +0 and last-digit rounding errors: in test 'family' (which applies a cone smoother to a regularly spaced set of spikes), centre points drop from highest to 0