-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Some arity exception message conversion tests failing under Clojure 1.10, 1.11 #791
Comments
Ah right, yeah fix welcome. |
Huh, getting 4 failures against clojure 1.11.1
I'll take a peek, if that's helpful. |
Thanks for taking a peek in advance! |
lread
added a commit
to lread/sci
that referenced
this issue
Aug 21, 2022
We were almost taking into account the `sci.impl.` fn name prefix that shows up in Clojure 1.10+, but not quite. Now also only applying arity conversion code to arity exception messages. We were previously accidentally only testing against Clojure 1.9.0, so these test failures went unnoticed. Fixes babashka#791
3 tasks
borkdude
pushed a commit
that referenced
this issue
Aug 22, 2022
We were almost taking into account the `sci.impl.` fn name prefix that shows up in Clojure 1.10+, but not quite. Now also only applying arity conversion code to arity exception messages. We were previously accidentally only testing against Clojure 1.9.0, so these test failures went unnoticed. Fixes #791
lread
added a commit
to lread/sci
that referenced
this issue
Aug 24, 2022
* master: Fix babashka#791: arity exception msgs for Clojure 1.10, 1.11 (babashka#793)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
version
master HEAD (at the time of this writing 4981762)
platform
jvm
problem
script/test/jvm
wants to test against clojure 1.9.0 and then clojure 1.10.2-alpha1, butclojure-1.10.2-alpha1
profile does not exists inproject.clj
.During
script/test/jvm
run you'll see:The result, I think, is that we repeat the clojure 1.9.0 test a second time.
next steps
Happy to PR if you let me know what you'd like to do today.
Maybe test against clojure 1.9.0 and clojure 1.11.1?
The text was updated successfully, but these errors were encountered: