On Fri, Oct 18, 2013 at 6:11 PM, Faré fah...@gmail.com wrote:
I'm curious about what happens to string with non-latin1 characters in
them:
do they cause the loading to abort, or are they interned as string
with different lengths
depending on the unicode support? (Similarly for latin1
For attached file unicode.lisp [...]
So allegro stores the strings in utf-8 (as confirmed by looking at a
trivial fasl), and when a non-latin1 (or cp1252) character is interned
from the fasl in a 8-bit variant, it becomes #\?. That makes sense.
I'm not sure how to make a latin1 string which is
If i run interactively I get Y U NO use stamp cache (I'm sure you know it
already):
bob:~ dcooper8$ cd genworks/cl/tests/asdf/asdf-macos/test
bob:test dcooper8$ /Users/dcooper8/genworks/cl-engines/ccl-mac-1.9/dx86cl64
--no-init --quiet
Welcome to Clozure Common Lisp Version 1.9-r15759
Oops, I should update the instructions on how to reproduce bugs at the
REPL,
by including a with-asdf-cache in them. I have no time to do that now,
but maybe you do.
Ok, I'll look at it.
Please see attached.
--
My Best,
Dave Cooper, Genworks Support
david.coo...@genworks.com,
Your attachment shows ccl failing on a test that I have disabled some time
ago,
and failure in test-force.
No, it doesn't. The only failing test in there is the test-force one.
My apologies, I was looking at a same-named older log.
Weird, it works for me on Linux.
But, it's very strange. I
On Sat, Oct 19, 2013 at 2:34 PM, Faré fah...@gmail.com wrote:
Now, it's possible that the test is failing to touch files in the
cache the same way that they are used in the test, because of all the
pathname normalizations that may happen, but that the discrepancy
somehow only shows up on
But I am still getting stamp-propagation failures on Windows with mlisp
after having run mlisp8 (and I think it would also fail if running mlisp8
after mlisp). I will send the console output from that separately.
That makes sense: the test includes a test of the time propagation bug
for the
But I am still getting stamp-propagation failures on Windows with mlisp
after having run mlisp8 (and I think it would also fail if running mlisp8
after mlisp). I will send the console output from that separately.
Said console output is attached.
I suspect this is indeed an issue with
On Sat, Oct 19, 2013 at 3:34 PM, Faré fah...@gmail.com wrote:
But I am still getting stamp-propagation failures on Windows with mlisp
after having run mlisp8 (and I think it would also fail if running
mlisp8
after mlisp). I will send the console output from that separately.
That makes
On Sat, Oct 19, 2013 at 5:33 PM, Dave Cooper david.coo...@genworks.comwrote:
Ok here's a patch for that.
It seems to fix things for allegro/Windows, but now it reared its head
again on sbcl/Windows.
Welp, it just happened again on alisp -- and that was in a clean build/
directory before
I committed a variant of your patch. See 3.0.2.30.
Can you send a failure log?
Touch is not part of Windows, but it's probably part of either cygwin
or msys or whichever add-on you run the test scripts with.
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
Yield to
On Sat, Oct 19, 2013 at 7:43 PM, Faré fah...@gmail.com wrote:
I committed a variant of your patch. See 3.0.2.30.
With this pulled, test-stamp-propagation started failing even more reliably
(on Windows only), usually on the first or second lisp being run.
I remembered reading somewhere (I
12 matches
Mail list logo
