This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-24
Channels
- # aleph (4)
- # beginners (93)
- # cider (7)
- # cljs-dev (16)
- # cljsrn (5)
- # clojure (192)
- # clojure-dusseldorf (3)
- # clojure-italy (14)
- # clojure-russia (16)
- # clojure-serbia (1)
- # clojure-spec (85)
- # clojure-taiwan (1)
- # clojure-uk (79)
- # clojurescript (188)
- # code-reviews (9)
- # core-async (2)
- # crypto (1)
- # cursive (26)
- # datomic (21)
- # heroku (1)
- # hoplon (3)
- # jobs (7)
- # jobs-discuss (20)
- # jobs-rus (13)
- # off-topic (77)
- # om (15)
- # onyx (23)
- # pedestal (94)
- # planck (11)
- # proton (10)
- # protorepl (1)
- # re-frame (16)
- # ring (22)
- # ring-swagger (9)
- # rum (2)
- # specter (18)
- # testing (2)
- # untangled (14)
- # vim (12)
- # yada (58)
@mfikes I’d be up for a box with that many cores 🙂 put me down
The problem with the Transit issue is that you essentially need such a box to repro the issue. Without it, you can't.
on a more serious note, are you sure that’s the commit which causes the regression?
it looks so.. inoffensive
Yes, I'm fairly certain. It almost, but not quite, deterministically fails every time with that commit, but not the one prior.
If anyone is interested in trying to repro downstream:
0. Get a dual-hexacore
1. git clone
and cd planck
2. CLJS_COMMIT=86f26bf267f1c729313320c38e53e64450c0e68d script/build
Good call @anmonteiro — I finally got the previous commit to fail in the same way. So, I'm off to do more bisecting.