-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lein-midje not working with high-level Leiningen tasks (in plugin projects) #47
Comments
I'm not sure that this is a right place... but I have a similar and strange behavior:
All tests passed, but I see "Error encountered performing task 'midje' with profile(s): 'dev'". PS: Yes, I have ":eval-in-leiningen true" in my project.clj |
This change is the cause. @marick introduced it because on some platforms the plugin took several seconds to shut down after all tests have been run. So I've been running |
lein-midje has bug marick/lein-midje#47 which prevents to run tests correctly on Travis CI
@xsc Thank you for the hint! I've downgraded lein-midje to the version 3.1.1 and it works pretty fine on Travis CI. Will it be fixed in future versions of the plugin? |
Well, this issue has been open for a year and three days now, so I'm not overly confident, the maintainers really see this as something that needs fixing... |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Travis CI does not work reporting that 'midje' is not a lein task. - Downgrading it to version 3.1.1 should now fix the problem (marick/lein-midje#47)
I've now put this on the trello board. The problem with fixing it is that understanding how Leiningen behaves has gotten a lot more difficult than it used to be. |
Trello card: https://trello.com/c/BzLO5BuU/17-lein-midje-not-working-with-high-level-leiningen-tasks-in-plugin-projects-47 Pull requests welcome. |
+1 |
Any news about this problem?.. |
Sorry for the delayed reply. I've moved from Clojure on the backend to Elixir. Because of that, I can't devote time to lein-midje. I will do what I can to transition it to anyone who wants to pick it up. |
Let's say I have the following in my
project.clj
:No tests are defined so far, so midje should not encounter any failures. I call:
Exit code is 1, things like TravisCI will fail. Note that this works fine for non-
:eval-in-leiningen
projects, the fact thatleiningen.core.main/exit
is called even if no failure is encountered just breaks testing of, e.g., plugin projects in that manner.The text was updated successfully, but these errors were encountered: