On Apr 17, 2010, at 3:50 PM, B Smith-Mannschott wrote:
On Sat, Apr 17, 2010 at 21:32, Stuart Halloway
wrote:
It's almost certainly the commit that added the InternalReduce
protocol:
5b281880571573c5917781de932ce4789f18daec.
I am slowly pounding my skull against this and would welcome any
On Sat, Apr 17, 2010 at 21:32, Stuart Halloway
wrote:
> It's almost certainly the commit that added the InternalReduce protocol:
> 5b281880571573c5917781de932ce4789f18daec.
>
> I am slowly pounding my skull against this and would welcome any help. It
> appears that the internal-reduce function fla
It's almost certainly the commit that added the InternalReduce
protocol: 5b281880571573c5917781de932ce4789f18daec.
I am slowly pounding my skull against this and would welcome any help.
It appears that the internal-reduce function flakes out and stops
working, but only intermittently.
If
I let Meheadable and George (my two macs) run clojure-contrib builds
while I was watching TV to get an idea of the probability of this
crash occurring was.
George, a 1 GHz PowerPC G4 (1 core) fails 37 of 59 builds (circa 63%)
Meheadable, a 2.2 GHz Core2Duo (2 cores) fails 48 of 132 builds (circa 3
On Sat, Apr 17, 2010 at 18:02, B Smith-Mannschott wrote:
> On Sat, Apr 17, 2010 at 15:45, B Smith-Mannschott
> wrote:
>> More oddness:
>>
>> If I remove all unit tests *except* test-compex-numbers, all is well:
>>
>> [INFO] [clojure:test {execution: test-clojure}]
>>
>> Testing clojure.contrib
On Sat, Apr 17, 2010 at 15:45, B Smith-Mannschott wrote:
> More oddness:
>
> If I remove all unit tests *except* test-compex-numbers, all is well:
>
> [INFO] [clojure:test {execution: test-clojure}]
>
> Testing clojure.contrib.test-complex-numbers
>
> Ran 8 tests containing 268 assertions.
> 0
More oddness:
If I remove all unit tests *except* test-compex-numbers, all is well:
[INFO] [clojure:test {execution: test-clojure}]
Testing clojure.contrib.test-complex-numbers
Ran 8 tests containing 268 assertions.
0 failures, 0 errors.
If I remove only test-complex-numbers, leaving a
On 16.04.2010, at 19:49, B Smith-Mannschott wrote:
> A few representative examples of the failures I'm seeing
>
...
> FAIL in (complex-conjugate) (run-test1347341999632195512.clj:44)
> expected: (= (conjugate (complex 1 2)) (complex 1 -2))
I'm building af2a730 "some tests for c.c.io byte-level support" of
clojure-contrib.
I'm seeing clojure.contrib.test-complex-numbers error out the maven
build with 4 failures and 253 errors on two of the five platforms at
my disposal.
Only my linux-based netbooks fail the build. JDK version does n
