Ah. This is probably the compiled version which fails. The interpreted version is the one I ran.On Thu, Apr 9, 2015 at 9:09 PM, Anton Vodonosov <avodonosov@yandex.ru> wrote:Reproduce it like this:
(ql:quickload :cl-cont-test)
(let ((rtest::*compile-tests* t)) (rtest:do-tests))
The RT test framework has two modes, rtest::*compile-tests* == t and nil.
cl-test-grid runs both modes.
> Did the cl-cont tests run in their own ABCL instance?
Yes, separate ABCL process.
Best regards,
- Anton
09.04.2015, 21:55, "Erik Huelsmann" <ehuels@gmail.com>:
> Hi Anton,
>
> On Tue, Apr 7, 2015 at 12:12 AM, Anton Vodonosov <avodonosov@yandex.ru> wrote:
>> 07.04.2015, 01:07, "Erik Huelsmann" <ehuels@gmail.com>:
>>>
>>> Bummer that the change causes regressions and no improvements.
>>
>> Note, we don't know exactly what of the changes between release 1.3.1 and the current dev version
>> causes the regressions, it's not necessary the last commit.
>
> Sure. That's no problem. However, I'm not understanding something: I tested the cl-cont LABELS-2 and -3 failures. On my own system they didn't fail. Is there something in the tester environment that could make it fail? Did the cl-cont tests run in their own ABCL instance? Or did they run after lots of other test in the same instance?
>
> Regards,
>
> --
> Bye,
>
> Erik.
>
> http://efficito.com -- Hosted accounting and ERP.
> Robust and Flexible. No vendor lock-in.
--