>
> No problem. Unfortunately, now "make check" breaks:
>
> Error: assertion failed: (eqv? (f32vector-ref old 6) (f32vector-ref new 0))
>
Ouch. I'm running make check with something based on the current
HEAD all the time, on what platform is this? Is the error consistently
appearing? If you
Hi!
Jim has encountered an issue with file-lock procedures.
The attached patch fixes this. While investigating I have noticed
that we don't actually check the locking procedures in our tests.
I shall think of a test for these (Bug for this is #1566).
Comments?
--
May you be peaceful, may you
Hi,
On Thu, 29 Nov 2018 11:42:36 +0100 felix.winkelm...@bevuta.com wrote:
>> On Wed, Nov 28, 2018 at 07:25:33PM +0100, Mario Domenech Goulart wrote:
>> > It looks like this patch (79cf7427, master) has broken "make
>> > bootstrap". Log attached (using CHICKEN 5.0.0 as CHICKEN).
>>
>> Right you
Hello Megane,
On Nov 30 2018, megane wrote:
Hi,
Here's another version that crashes quickly with "very high
probability".
...
24 Error: (mutex-unlock) Internal scheduler error: unknown thread state
25 #
26 ready
This bears an uncanny resemblance to scheduler issues I've
Hi,
Here's another version that crashes quickly with "very high
probability".
(cond-expand
(chicken-5 (import (chicken base))
(import (chicken time))
(import srfi-18))
(else (import chicken)
(use srfi-18)))
(define m (make-mutex))
(print "@@ " (current-thread)
