OK, that makes sense. These tests were passing for me on the Mac, but
brew has ECL 16.1.3 instead of 16.1.2.
On 1 Sep 2018, at 7:26, Marius Gerbershagen wrote:
The patch works exactly as it should. All it does is to exit the
current
process with a return code of 1 if the process lands in
Am 01.09.2018 um 04:36 schrieb Faré:
> On Thu, Aug 30, 2018 at 1:46 PM Marius Gerbershagen
> wrote:
>> The test-require.script test fails because it tries to require
>> the :rt module which is deprecated on the develop branch and no longer
>> build by default. A simple fix is to use the :socke
Unfortunately, this patch doesn't seem to work. Maybe it interferes
with condition handlers? At any rate, after I insert it into
script-support.lisp I now get two *new* test failures in
package-inferred-system-test.script and
test-defsystem-depends-on.script. I get a message that
```
Top l
On 31 Aug 2018, at 10:35, Marius Gerbershagen wrote:
This is most likely a bug in ECL. I recommend trying out a newer
version
of ecl (16.1.3 or the current develop branch from the git repository).
I see your point, but have two comments:
1. If this really *is* an ECL bug, then shouldn't the
I'm experimenting with your changes now but, for some reason that I
don't understand, when I run the tests as `make l=ecl` interactively on
Ubuntu (using the Ubuntu ECL package `16.1.2-3`), signals are throwing
me into the interactive debugger, instead of being caught. I have no
idea why this
Thank you very much for these, Marius. I will look into fixing them
directly. One question - do I need to check for ECL version number when
requiring sockets in the test? I.e., to I need to test with `:rt` in
older versions and `:sockets` in newer? Or will `:sockets` work in older
versions o
Harmless in the sense that ECL doesn't crash or throw me in the
interactive debugger. Besides, the test failures seem to be easily
fixed. The test-require.script test fails because it tries to require
the :rt module which is deprecated on the develop branch and no longer
build by default. A simple
Hi Robert,
Am 23.08.2018 um 22:22 schrieb Robert Goldman:
> My Jenkins job is failing to test ECL successfully. What's interesting
> is that it looks like the tests are successful, but the checker is
> failing. Here's what I see in the transcript:
>
> These two expressions fail comparison with
