freenode/#clasp - IRC Chatlog
Search
7:42:17
Colleen
kpoeck: drmeister said 10 hours, 51 minutes ago: No - nobody is running the regression tests yet - we need to get them into the build-bot.
7:42:17
Colleen
kpoeck: drmeister said 10 hours, 23 minutes ago: What tests fail with compile-file-parallel?
7:42:17
Colleen
kpoeck: drmeister said 4 hours, 3 minutes ago: I ran the ansi-test per your instructions twice - once with compile-file-parallel and another with compile-file-serial. In each case I get 267 out of 21840 total tests failed. What failures do you see? One interesting thing is there are a couple of tests that fail in serial and not in parallel and vice-versa to give the same total! eg: in parallel FBOUNDP.8 fails and in serial FBOUNDP.ERROR.3
7:42:17
Colleen
kpoeck: drmeister said 4 hours, 3 minutes ago: Also in parallel mode FUNCALL.ERROR.3 fails and in serial mode FUNCALL.ERROR.1 fails.
7:43:14
kpoeck
i believe right now they won't work in parallel mode, since that does not seem to handle logical pathnames well
7:44:28
kpoeck
https://github.com/clasp-developers/clasp/pull/918 tries to address that (and other problem from croscompiling sbcl)
12:03:18
kpoeck36
https://github.com/kpoeck/clasp/blob/feature-varios-compile-file-fixes/src/lisp/kernel/cmp/compile-file-parallel.lsp#L351 specifically
12:04:31
kpoeck36
I believe something like "make check" would be best to run the regression-tests (and perhaps make check-extended) for the ansi-tests
12:50:59
drmeister
I thought the regression tests were being run in the buildbot - I'll check when I talk with cracauer
12:54:02
kpoeck36
as I said this morning, I believe the regression tests currently don't run with the parallel compiler w/o my PR 918
12:55:35
kpoeck36
the company I work for - GFT - seems now to bet on googles bazel (https://bazel.build/)
12:56:17
drmeister
How does bazel help? It sounds like you have to explicitly define the dependencies by hand?
12:57:28
drmeister
Am I missing something here? Going with a Java based build system rather than adding parallel compilation to asdf? It sounds crazy.
12:58:04
drmeister
I turned off compile-file-parallel again - because it massively slows down quicklisp compilation on linux.
13:03:24
drmeister
What's the problem with pathnames in compile-file-parallel? Because I fear I might have propagated the problem to compile-file-serial.
13:03:46
drmeister
I'm running fast and loose with pathnames when I created the .faso and .fasp extensions. Am I breaking rules?
13:04:25
drmeister
kpoeck36: I'm looking at your pull request and I see changes related to pathnames - but I can't figure out what the overarching problem is.
13:05:54
drmeister
It's messier and more complicated than that so I need to get it straight so I don't screw up more code.
13:06:53
drmeister
I hate the idea of a .o file being a .faso file internally - that seems very wrong.
13:07:16
drmeister
But .fasl could be a .fasp file under the hood. We are free to define that I think.
13:08:33
drmeister
:object-type :fasl -> .fasl (but it's actually .fasp file and is recognized as NOT being a .dylib/.so by its magic number)
13:47:10
drmeister
The stuff about faso/fasp file extensions that kpoeck36 has identified may be causing problems.
13:48:17
drmeister
I look at the source and I can't deduce what the underlying problem is. Something about compile-file-parallel not handling logical pathnames.
13:48:42
drmeister
I might be confused in thinking there is something wrong with my changing file extensions from .o/.fasl to .faso/.fasp
13:49:45
drmeister
kpoeck36 says that the regression tests would show the problem but I don't know how to run the regression tests (I was mistakenly running the ansi-tests all day yesterday)
15:35:17
Bike
If I do (mp:make-condition-variable 'test), i get an error about an odd number of keyword arguments
15:35:36
Bike
but as far as I can tell, make-condition-variable is defined with CL_DEF_CLASS_METHOD and CL_LAMBDA(&optional name);
15:39:39
drmeister
The ultimate arbiter of what a lambda list looks like for a function is in build/boehm/generated/*.h
15:40:02
drmeister
expose_function(core::magic_name("MP:make_ConditionVariable"),&ConditionVariable_O::make_ConditionVariable,R"lambda((&optional name))lambda");
15:40:55
Bike
okay, but the actual function takes a keyword argument, so it's not actually ultimate.
15:41:40
drmeister
(wrap-c++-function (core:magic-intern "mp__make_condition_variable") () (&key name) "wrapped_mp__make_condition_variable_core__T_sp" )
15:42:23
Bike
The lambda list displays as (&optional name) but the function actually has (&key name)
15:44:41
Bike
i'm going through mp right now to document things and there are a lot of little inconsistencies like this. ill try to clean them up
15:45:25
drmeister
mp__make_condition_variable lispifies to the same thing. We should catch that and warn about it. It's a bad source of errors.