June 2018 - asdf-devel - mailman3.common-lisp.net

Is anyone actually using the deferred warnings code?
by Robert Goldman 06 Aug '18

06 Aug '18

AFAICT, it is disabled by default, and it is not documented in the ASDF manual. So is this code even live, except for in the test scripts? It was pretty painful to get this to work because it relies on unexported (and hence unstable) SBCL internals. My *guess* is that this was originally done as a way to dispense with `WITH-COMPILATION-UNIT` and hence potentially parallelize the compilations. If no one is even using it, I am tempted to move it to be a contrib and drop it from the tests and maintenance as part of core ASDF. Maybe it would be better as a part of a POIU extension to ASDF, and relieve me of dealing with these SBCL compiler internals? Cheers, r

3 3

POIU is bitrotten
by Faré 26 Jul '18

26 Jul '18

In case anyone cares (I suppose no one does), POIU, the parallel operator on independent units, that parallelizes compilation (but not loading) of ASDF component, with various options regarding determinism or non-determinism, is current bitrotten and not working on ASDF 3.3.2.2, and I disabled its functionality. I don't have the time or interest to fix it (I haven't been using CL at work for five years, and have stopped using it for new personal projects). The other option I know to parallelize a CL build is bazelisp (the Lisp support for bazel.build), which I would bet is also bitrotten, since I haven't touched it in years, either. [An earlier option I worked on, XCVB, has bitrotten long ago.] I am still available for advice in case someone wants to fix things — better ask before the information gets evicted to long-term storage. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Superstition brings bad luck. — Saul Gorn

2 4

A thing I should know myself....
by Robert Goldman 24 Jun '18

24 Jun '18

I have a library that provides `DEF-UNIMPLEMENTED` as a macro for defining stub functions. When you compile a file with unimplemented functions, you get a warning of the type `FOO:UNIMPLEMENTED-STUB` in my library `FOO`. I'd like to put in an asdf system definition a file spec something like this: ``` (:file "file-with-stubs" :method (:around (o c)   (handler-bind ((foo:unimplemented-stub #'(lambda (c) (print c) (muffle-warning c)) (call-next-method))) ``` but, of course, the package `foo` doesn't exist when this is read (although I could put `(asdf:load-system "foo")` upstream of the enclosing defsystem). This isn't a case that's nicely consistent with Faré's hack for translating strings or keyword symbols, nor does it seem easy to use `find-symbol` for this purpose. Thoughts? thanks, r

3 4

gentoo package broken
by Konstanski, Carlos 23 Jun '18

23 Jun '18

The gentoo packaging for the new ASDF version is broken. !!! Fetched file: asdf-3.3.2.2.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 484988 !!! Expected: 487861 -- Carlos Konstanski

3 2

ASDF with-muffled-compiler-conditions gripe`
by Cyrus Harmon 11 Jun '18

11 Jun '18

Dear ASDF folks, I was trying to trace calls to compile-file today and noticed that the with-muffled-compiler-conditions form in uiop:compile-file* muffles trace output. Is there anyway to make it not do that? thanks, Cyrus

2 5

locating a source directory
by Didier Verna 08 Jun '18

08 Jun '18

Hello, I would like to find the source directory of an installed ASDF system even if it's not loaded and even if some of its dependencies are not installed (so it couldn't be loaded anyway). It seems that I can't use SYSTEM-SOURCE-DIRECTORY in such a case. What should I do? Thanks! -- Resistance is futile. You will be jazzimilated. Jazz site: http://www.didierverna.com Other sites: http://www.didierverna.info

1 1

Introspecting test suite passing/failing
by Mark Evenson 07 Jun '18

07 Jun '18

We use ASDF to encapsulate the building and testing many systems under an automated test runner. For a given system, ASDF:TEST-SYSTEM always returns boolean truth as long as the invocation of the underlying test suite succeeds. This means there is no programatic way to provide a boolean as to whether all the tests passed or not on the invocation of a test suite to the invoker of ASDF:TEST-SYSTEM. It seems that this issue has been raised before, as the ASDF manual documents TEST-OP <https://www.common-lisp.net/project/asdf/asdf/Predefined-operations-of-ASDF…> with: > The results of this operation are not defined by ASDF. It has proven difficult > to define how the test operation should signal its results to the user in a way > that is compatible with all of the various test libraries and test techniques > in use in the community, and given the fact that ASDF operations do not return > a value indicating success or failure. For those willing to go to the effort, > we suggest defining conditions to signal when a test-op fails, and storing in > those conditions information that describes which tests fail. Is this still the best current practice to introspect the situation of failing tests? Can someone point me to an example implementation of this technique? -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

3 12

Pushed fix for SBCL deferred warnings as 3.3.2.1
by Robert Goldman 05 Jun '18

05 Jun '18

Squashed and merged this, pushed, and deleted the feature branch. Thanks to Eric Timmons for detecting the bug, and to Fare and Attila for reviewing the fix. We can think about a bug fix release sometime soon. I think right before merging the syntax fix, which should give us the basis for 3.4 Best to all, r

2 1

Last call for suggestions on merge request 95 (fix deferred warnings on SBCL)
by Robert Goldman 01 Jun '18

01 Jun '18

I believe all the critiques are now addressed. I am rerunning the tests on Mac and Linux, and if all goes well with squash-merge this topic branch to master. So if there are any last issues, please let me know. thanks, r

1 0