-
-
Notifications
You must be signed in to change notification settings - Fork 649
cider-test-run-test picks up the wrong var to test when using metadata #3758
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
Comments
If you can point me to the relevant code (and test), I can look into fixing this. |
Interesting catch! The Elisp-level parsing happens at |
Hmmm. I haven't debugged this thoroughly, but when I looked at the source code of
Thanks for the hint, btw! |
Nice! Then it's primarily an issue in https://github.com/clojure-emacs/clojure-mode , although it seems good to keep this one here too. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed soon if no further activity occurs. Thank you for your contribution and understanding! |
Fixed by clojure-emacs/clojure-mode#682 |
Expected behavior
cider-test-run-test
runscomplex-metadata
test.Actual behavior
cider-test-run-test
runsno-metadata
test.Steps to reproduce the problem
Create a fresh project with a test namespace.
Evaluate all forms and then
no-metadata
-> all's goodsimple-metadata
-> all's goodcomplex-metadata
-> it'll actually run the test no-metadataThe problem is likely with cider, because if I run the test with
M-x nrepl-toggle-message-logging
I see the following nrepl messageMeaning that cider actually picks up the wrong var to test.
Environment & Version information
CIDER version information
However, I've installed cider through melpa-unstable and it's installed in the directory
cider-20241115.343
. I.e. I'm running https://github.com/clojure-emacs/cider/tree/c228dec27df6b2c68262f17158208fe699e1ce02.Emacs version
29.4
I haven't ruled out interaction with other emacs packages. Although, my initial guess is that it's unlikely.
Operating system
ArchLinux
The text was updated successfully, but these errors were encountered: