This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-24
Channels
- # beginners (12)
- # cider (3)
- # clara (3)
- # cljs-dev (3)
- # cljsrn (19)
- # clojure (83)
- # clojure-android (1)
- # clojure-dev (15)
- # clojure-dusseldorf (1)
- # clojure-greece (30)
- # clojure-italy (10)
- # clojure-madison (1)
- # clojure-nl (6)
- # clojure-russia (274)
- # clojure-spec (51)
- # clojure-uk (31)
- # clojurescript (38)
- # core-async (7)
- # cursive (11)
- # datascript (1)
- # datomic (63)
- # emacs (10)
- # figwheel (1)
- # hoplon (27)
- # jobs (11)
- # klipse (4)
- # lein-figwheel (1)
- # lumo (6)
- # nyc (1)
- # off-topic (278)
- # om (12)
- # pedestal (10)
- # protorepl (31)
- # re-frame (13)
- # reagent (23)
- # remote-jobs (1)
- # spacemacs (9)
- # untangled (24)
- # yada (54)
@alexmiller i just noticed that the spec matrix tests are failing
it is known to me
it’s a CLJ-1544-ish issue with the ordering of load between .clj and .class versions of the spec protocol
we’ve worked around this several times now - the problem is that core loads spec early and it can load the .clj files instead of the .class files during compilation of spec itself
still trying to decide how to fix it. it’s particularly annoying in that doing local builds of clojure makes the file times newer and masks the problem, so it’s annoying to debug. also, the clojure-maven-plugin uses a Java HashSet internally that affects the ordering of the classpath differently on different jdks
all of that affects the random-seeming set of results in the build matrix
once everything aot’ed, there’s no issue
I would actually like to add some way to turn off the core spec loading (or not turn it on by default)
I had that in some early versions and we weren’t sure we needed it so it fell out before release