Here's what I see in the Jenkins log: ``` ;;; Loading "/var/lib/jenkins/workspace/asdf/test/file1.lisp" ;;; Warning: Computing just-done stamp in plan NIL for action (PREPARE-SOURCE-OP "test-multiple-too"
> ;;; Warning: Computing just-done stamp in plan NIL for action > (PREPARE-SOURCE-OP > > "test-multiple-too" >"file2"), but > dependency (LOAD-SOURCE-OP > > "test-multiple-too" > > "file1") wasn't done yet! > > Note the warning --
On 20 Feb 2018, at 10:49, Faré wrote: I don't know what the root cause is here, but this looks like the same bug that is supposed to be fixed, and the fix works for me. Does Jenkins use some fancy filesystem setup that confuses the timestamp checking? It might. Jenkins does everything in a
I think we are ready to release 18.104.22.168 as 3.3.2 I am quite busy this week, so it will probably take me a while to get through the necessary drudgery to actually make the release, but there is a good population of fixes to send out, so I'll make it happen. Best, r
I still see these "dependency not done" warnings in test-bundle on SBCL and other implementations (I haven't checked them all, but at least my big three: SBCL, Allegro, and CCL). ``` Running test-bundle.script with sbcl-1.4.3-macosx-x64 ; loading
This does seem to illustrate an issue with the current "export everything that's in UIOP" strategy. Should we consider changing this policy? Or, if we have "internal" functions that we don't want to be visible through `UIOP/DRIVER`, should we simply not export them from the sub-packages and