Tests all pass on my Windows VM (thanks to Dave Cooper!).
Tests all pass on Mac.
Running tests on Linux.
After that propose to release 3.1.6.
I'd like to get the UIOP fix for SBCL on Windows in place before the
release, but still have no bug report, so am not sure how to replicate
or fix.
Last c
OK, somehow, although all of the ALLEGRO variants specify that we should
be using buildi.exe or build.exe, when we actually get to test-program,
it's using alisp.exe, which seems to cause breakage.
I am looking at the output of ALL-ALLEGRO-VARIANTS.
So what is crushing the allegro executable and
On Tue, Sep 29, 2015 at 2:46 PM, Robert Goldman wrote:
> I'm getting what look like spurious failures on tests of "allegro" in
> test-program.script.
>
> I *believe* that what's going wrong here is that lisp-invocation is
> getting confused about how to find the right ACL runtime.
>
> If you look
I'm getting what look like spurious failures on tests of "allegro" in
test-program.script.
I *believe* that what's going wrong here is that lisp-invocation is
getting confused about how to find the right ACL runtime.
If you look at run-tests.sh, you will see that "ALLEGRO" is initially
bound usin
On 2015/9/29 17:34, Faré wrote:
> On Tue, Sep 29, 2015 at 11:03 AM, Mark Evenson wrote:
>> I wanted to confirm with ASDF developers that as far as I can tell from
>> wrangling with UIOP:RUN-PROGRAM, it isn't going to do what I want
>> because there is no "asynchronous" mode.
> UIOP:RUN-PROGRAM i
> In a potentially memory constrained environment, I need to portably
> (across sbcl and ccl at least) process a potentially large (multiple
> GiB) stream of bytes output from a Linux command. For the curious,
> "process" here means encrypt with a block cipher and push to the
> network; whereas th
When I run test all on Windows, the SBCL tests fail in a spurious way.
I get an error that lisp couldn't rename f:\asdf\build\dir1\foo0.asd to
f:\asdf\build\dir1\foo1.asd.bak
AFAICT this is because CREATE-ASD-FILES in test-configuration.script
uses :if-exists :rename-and-delete when it's creating
On Tue, Sep 29, 2015 at 12:28 PM, Robert Goldman wrote:
> When I run test all on Windows, the SBCL tests fail in a spurious way.
>
> I get an error that lisp couldn't rename f:\asdf\build\dir1\foo0.asd to
> f:\asdf\build\dir1\foo1.asd.bak
>
> AFAICT this is because CREATE-ASD-FILES in test-configu
On Tue, Sep 29, 2015 at 12:14 PM, Mark Evenson wrote:
> Is their any informal ASDF policy on the stability unexported symbols
> like UIOP::%RUN-PROGRAM? I suspect y'all reserve the right to yank the
> rug at any point, right? Given that UIOP::%RUN-PROGRAM abstracts the
> Lisp implementations cap
On Tue, Sep 29, 2015 at 11:03 AM, Mark Evenson wrote:
> I wanted to confirm with ASDF developers that as far as I can tell from
> wrangling with UIOP:RUN-PROGRAM, it isn't going to do what I want
> because there is no "asynchronous" mode.
UIOP:RUN-PROGRAM itself is synchronous only, but its intern
In a potentially memory constrained environment, I need to portably
(across sbcl and ccl at least) process a potentially large (multiple
GiB) stream of bytes output from a Linux command. For the curious,
"process" here means encrypt with a block cipher and push to the
network; whereas the UNIX com
11 matches
Mail list logo
