This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-17
Channels
- # alda (5)
- # bangalore-clj (1)
- # beginners (9)
- # bigdata (1)
- # boot (51)
- # carry (1)
- # cider (9)
- # cljs-dev (22)
- # clojars (39)
- # clojure (118)
- # clojure-brasil (1)
- # clojure-czech (8)
- # clojure-france (2)
- # clojure-italy (5)
- # clojure-korea (9)
- # clojure-russia (9)
- # clojure-spec (17)
- # clojure-uk (42)
- # clojurescript (48)
- # core-async (1)
- # emacs (3)
- # figwheel (1)
- # funcool (3)
- # hoplon (39)
- # klipse (51)
- # lein-figwheel (4)
- # leiningen (2)
- # luminus (5)
- # off-topic (245)
- # om (18)
- # onyx (19)
- # parinfer (1)
- # pedestal (18)
- # re-frame (47)
- # reagent (19)
- # ring-swagger (1)
- # specter (18)
- # untangled (93)
- # vim (8)
- # yada (56)
Sounds awesome but we should probably loop in Alex Miller, I'd rather it be an official thing
I have Planck master soaking an experimental ClojureScript compiler patch with :fn-var (not (:macro sym-meta))
to see if it can hold up over time.
we can definitely set something up in CI if someone can describe how to invoke it to me
there’s something working in this repo: https://github.com/ducky427/clojurescript/commit/2e1ea5f2196b12eaa6dce08d410ec8886d248b45
I don’t know why running the tests in a container is necessary, but there might be a reason
@alexmiller happy to guide you through the process of setting up the dependencies and running the necessary tests
TD;DR would be ./script/bootstrap
to set up deps, then
lein test ;; tests the compiler infrastructure
script/test ;; runs the core lib tests in advanced mode
script/test-simple ;; runs core lib tests with simple optimizations
script/test-self-host ;; tests bootstrapped ClojureScript infrastructure
script/test-self-parity ;; same as script/test but JVM-less (self-host)
ah I think I remember why the Dockerfile was there. I think it simplified having the JS engines for testing
in any case, there needs to be some setting up of environment variables with the location of the JS engines (V8, JavaScriptCore, SpiderMonkey and Nashorn)
they’re detailed in this wiki page: https://github.com/clojure/clojurescript/wiki/Running-the-tests
(the self-parity and self-host tests assume Node.js is installed)
ah, yeah I’ve been through this locally
I’m not going to get to it today but maybe later this week
@alexmiller awesome. let me know if there’s anything I can do to help
I do think we should have some story for Node.js since that’ll be the simplest way to test core.async
etc.
@dnolen does core.async
rely on any Node.js specific features?
if it doesn’t I don’t see why it is different from testing with V8
@anmonteiro there is no async mechanism in naked JS environments
ah right, that’s true