Warning: Computing just-done stamp in plan NIL for action
Robert Goldman
rpgoldman at sift.info
Wed Oct 18 13:39:03 UTC 2017
Is this system somewhere available (e.g., GitHub) so we could try to
replicate?
For that matter, could we break on signals and get a backtrace?
thanks,
r
On 18 Oct 2017, at 8:25, Chream iz wrote:
> Hi, I am also getting this error when trying to run (asdf:test-system
> ....). It is also not finding the test-files but that might be an but
> in the prove package?
>
> Summary:
> All 0 files passed.
> WARNING:
> Computing just-done stamp in plan NIL for action
> (ASDF/LISP-ACTION:TEST-OP
> "iparse"), but
> dependency (ASDF/LISP-ACTION:TEST-OP
> "iparse-test")
> wasn't done yet!
>
>
> system asd:
>
> #|
> This file is a part of iparse project.
> Copyright (c) 2017 Christopher Eames (chream) (chream at gmx.com)
> |#
>
> #|
> Author: Christopher Eames (chream) (chream at gmx.com)
> |#
>
> (in-package :cl-user)
> (defpackage iparse-asd
> (:use :cl :asdf))
> (in-package :iparse-asd)
>
> (defsystem iparse
> :version "0.1.1"
> :class :package-inferred-system
> :author "Christopher Eames (chream)"
> :license "MIT"
> :depends-on ("iparse/src/iparse")
> :description "A small parsing and data structure library."
> :long-description
> #.(with-open-file (stream (merge-pathnames
> #p"README.markdown"
> (or *load-pathname*
> *compile-file-pathname*))
> :if-does-not-exist nil
> :direction :input)
> (when stream
> (let ((seq (make-array (file-length stream)
> :element-type 'character
> :fill-pointer t)))
> (setf (fill-pointer seq) (read-sequence seq stream))
> seq)))
> :in-order-to ((test-op (test-op iparse-test))))
>
> (register-system-packages
> "closer-mop"
> '(:c2mop :closer-common-lisp :c2cl :closer-common-lisp-user
> :c2cl-user))
> (register-system-packages
> "lil"
> '(:lil/core :interface :pure :smltateful :classy :posh :lil/test))
>
> (register-system-packages "iparse/src/all" '(:iparse.dev))
> (register-system-packages "iparse/src/formats" '(:iparse.formats))
> (register-system-packages "iparse/src/utils" '(:iparse.utils))
> (register-system-packages "iparse/src/iparse" '(:iparse))
> (register-system-packages "iparse/src/types" '(:iparse.types))
>
>
>
> Test system asd:
>
> #|
> This file is a part of iparse project.
> Copyright (c) 2017 Christopher Eames (chream) (chream at gmx.com)
> |#
>
> (in-package :cl-user)
> (defpackage iparse-test-asd
> (:use :cl :asdf))
> (in-package :iparse-test-asd)
>
> (defsystem iparse-test
> :author "Christopher Eames (chream)"
> :license ""
> :depends-on (:iparse
> :prove)
> :components ((:module "t"
> :serial t
> :components
> ((:file "utils")
> (:test-file "utils-test")
> (:test-file "read-single-test-byte")
> (:test-file "read-single-test-sequence")
> (:test-file "read-single-test-composite")
> (:test-file "read-single-test-class")
> (:test-file "byte")
> (:test-file "macro")
> (:module "new"
> :serial t
> :components
> ((:test-file "basic-tests"))))))
> :description "Test system for iparse"
>
> :defsystem-depends-on (:prove-asdf)
> :perform (test-op :after (op c)
> (funcall (intern #.(string :run-test-system)
> :prove-asdf) c)
> (asdf:clear-system c)))
>
>
> Christopher
>
>
>
>
>> On 18 Oct 2017, at 15:05, Faré <fahree at gmail.com> wrote:
>>
>> Can you anonymize it and send it? Or extract a minimal failure case?
>> I
>> can't reproduce at home, nor imagine what could be happening.
>>
>> Anton, could you test the syntax-control branch with cl-test-grid,
>> and
>> grep the results for expansions of the format string "Computing
>> just-done stamp in plan ~S for action ~S, but dependency ~S wasn't
>> done yet!" ?
>>
>> —♯ƒ • François-René ÐVB Rideau
>> •Reflection&Cybernethics• http://fare.tunes.org
>> Mathematics is as little a science as grammar is a language. —
>> Ernst Mayr
>>
>>
>> On Wed, Oct 18, 2017, 08:11 Stas Boukarev <stassats at gmail.com> wrote:
>>>
>>> It's a work file, can't publish it. But it's just a defsystem with
>>> depends-on and components.
>>>
>>> On Wed, Oct 18, 2017 at 2:46 PM Faré <fahree at gmail.com> wrote:
>>>>
>>>> It's hard to tell without seeing the .asd file. The message says
>>>> that
>>>> you completed the load-op of the system, but somehow you never did
>>>> the
>>>> define-op of the system (the new action that tracks the loading of
>>>> .asd files so that defsystem-depends-on can be properly staged).
>>>>
>>>> Can you tell us more about the "non-complicated" features that you
>>>> use? Do you follow the "best practices" document?
>>>> https://github.com/fare/asdf/blob/master/doc/best_practices.md
>>>>
>>>> —♯ƒ • François-René ÐVB Rideau
>>>> •Reflection&Cybernethics• http://fare.tunes.org
>>>> Don't forget your daily prayer to Baah-kup,
>>>> the God of data storage and recovery!
>>>>
>>>>
>>>>
>>>> On Wed, Oct 18, 2017 at 7:35 AM, Stas Boukarev <stassats at gmail.com>
>>>> wrote:
>>>>> More new warnings from ASDF 3.3, this time I have no idea what it
>>>>> means.
>>>>>
>>>>> WARNING:
>>>>> Computing just-done stamp in plan NIL for action
>>>>> (ASDF/LISP-ACTION:LOAD-OP
>>>>> "system"), but
>>>>> dependency (ASDF/FIND-SYSTEM:DEFINE-OP
>>>>>
>>>>> "system") wasn't done yet!
>>>>>
>>>>> The .asd file is not public, but it looks perfectly normal without
>>>>> using any
>>>>> complicated features.
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/asdf-devel/attachments/20171018/841bae0a/attachment.html>
More information about the asdf-devel
mailing list