This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-30
Channels
- # admin-announcements (13)
- # announcements (2)
- # avi (1)
- # aws (10)
- # beginners (427)
- # boot (3)
- # cider (4)
- # clara (26)
- # cljs-dev (21)
- # cljsrn (24)
- # clojure (205)
- # clojure-dev (32)
- # clojure-india (26)
- # clojure-japan (1)
- # clojure-russia (256)
- # clojurescript (41)
- # clojurex (1)
- # cursive (38)
- # datavis (99)
- # datomic (15)
- # emacs (19)
- # events (2)
- # funcool (5)
- # immutant (45)
- # ldnclj (3)
- # om (60)
- # omnext (4)
- # onyx (383)
- # overtone (7)
- # parinfer (1)
- # re-frame (3)
- # reagent (7)
- # ring (1)
- # testing (5)
@martinklepsch: I ran your port of collection check against the Lean HAMT port. It worked in the browser (chromium) up to 1000000 tests but fails on node (4.2.2) and doesn't print out the action that it fails on
I've only tried my machine so far, I'll keep you updated on anything new I find
@spinningtopsofdoom: I have an idea of why it's not printing the failure (test.chuck not reporting a :shrunk on an exception). If I want to try it in my machine, what do I need? I mean, can I get the Lean HAMT port? About collection-check I guess it's @martinklepsch fork
You'll need to get lean map (here https://github.com/bendyworks/lean-map). Look in the script directory for the node / browser repls.
This is the setup you'll need for the CLJS port of collection check 1. git clone https://github.com/martinklepsch/test.chuck.git 2. cd test.chuck; git checkout extensible-shrunk-report; lein install 3. git clone https://github.com/martinklepsch/collection-check-1.git 4. cd collection-check-1; boot build-jar 5. use [collection-check "0.1.7-SNAPSHOT”]
AFAICT it's only failing in node
Feel free to ping me with any help you need to get anything setuo
Cool @spinningtopsofdoom, will let you know about any news
My collection check fork uses latest test.chuck and should properly report minimal cases
even when on exceptions out of assertions @martinklepsch?
Maybe that's not the issue, but I think test.chuck won't be reporting failures in that case (thought the :shrunk report mechanism)
@nberger: it's been a while... Not 100% sure but I thought I checked this
@martinklepsch: No worries. I'm not 100% sure if that's the issue either. I'll let you both know of any finding
@nberger and @martinklepsch I'm running (cc/assert-map-like 100 (.-EMPTY cljs.lean-map.core/PersistentHashMap) (gen/tuple gen/int) (gen/tuple gen/int))
and getting
FAIL in () (collection_check/core.js:540:53)
map-like
expected: (= (hash a) (hash b))
actual: (not (= -1161039890 -1296016722))
In both the browser and node repls with Cursive.
I'll take a look later. At first sight I'd say it's not what I was talking about an exception not in an assertion...
@spinningtopsofdoom: are you running my collection check fork?
I may have gotten some setup messed up I'll retry building your forks tonight