Skip to content
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

Exceptions are not reported correctly in 1.12.4-eap1 #2700

Closed
cursive-ide opened this issue May 29, 2022 · 1 comment
Closed

Exceptions are not reported correctly in 1.12.4-eap1 #2700

cursive-ide opened this issue May 29, 2022 · 1 comment
Labels
bug Marks issues describing bugs eap-only Marks issues describing bugs in EAP releases
Milestone

Comments

@cursive-ide
Copy link
Owner

The following test reports an error at the end of the test run, but doesn't indicate anywhere where the error happened:

(deftest foo
  (/ 1 0)
  (is (= 1 1)))

Additionally, no exceptions are logged to the console any more.

@cursive-ide cursive-ide added bug Marks issues describing bugs eap-only Marks issues describing bugs in EAP releases labels May 29, 2022
@cursive-ide cursive-ide added this to the 1.12.4 milestone May 29, 2022
@cursive-ide cursive-ide modified the milestones: 1.12.4, 1.12.4-eap2 May 30, 2022
@tomasd
Copy link

tomasd commented May 30, 2022

I have experienced this problem in 1.12.4-eap1.

I'm not sure if it's the same issue but in 1.12.4-eap2, but in some specific case the error is reported in the function in another namespace:

Snímka obrazovky 2022-05-30 o 12 03 21

(ns my_test
  (:require [clojure.test :refer :all])
  (:require [myproject-shared-app-utils :as utils]))


(deftest my-test
  (utils/gen-data))

Here are the files:

(ns myproject-shared-app-utils
  (:require
    [clojure.test :refer :all]
    [com.stuartsierra.component :as component]))


(defn gen-data []
  (/ 1 0))

Note that com.stuartsierra.component in latter is unused, if I uncomment it, then everything works OK. In the real project the namespaces are much longer but it looks like I've experienced the behaviour if there were multiple other function calls, commenting them out "fixed" the reporting.

I can create a new issue if it's not related to this one.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Marks issues describing bugs eap-only Marks issues describing bugs in EAP releases
Projects
None yet
Development

No branches or pull requests

2 participants