Skip to content
Discussion options

You must be logged in to vote

Eask attempts to load the complete package metadata, including all dependencies, to avoid potential errors. Because there is no guaranteed way to determine whether a package has dependencies, Eask runs package-initialize on every execution (eask test ert). It might be possible to infer whether initialization is necessary by inspecting the package’s dependency list.

You can do something like this to get away from this:

(add-hook 'eask-before-test/ert-hook
          (lambda () (advice-add 'eask-pkg-init :override #'ignore)))

Eask does not enforce loading package metadata in the command eask test ert-runner, as this behavior is entirely determined by the ert-runner package itself. 🤔

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@avishefi
Comment options

Answer selected by avishefi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants