This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-06
Channels
- # aleph (15)
- # beginners (40)
- # boot (14)
- # cider (90)
- # cljs-dev (132)
- # cljsrn (25)
- # clojars (7)
- # clojure (188)
- # clojure-chicago (4)
- # clojure-dusseldorf (1)
- # clojure-greece (9)
- # clojure-italy (43)
- # clojure-russia (16)
- # clojure-sg (7)
- # clojure-spec (39)
- # clojure-uk (81)
- # clojurescript (170)
- # component (5)
- # core-async (7)
- # cursive (49)
- # data-science (65)
- # datascript (3)
- # datomic (27)
- # graphql (3)
- # hoplon (4)
- # instaparse (56)
- # klipse (129)
- # leiningen (1)
- # lumo (28)
- # off-topic (4)
- # om (15)
- # onyx (54)
- # overtone (7)
- # pedestal (7)
- # re-frame (9)
- # reagent (72)
- # ring (33)
- # ring-swagger (2)
- # spacemacs (1)
- # untangled (19)
- # vim (2)
- # yada (12)
@moxaj did you fix this? ^
is that the mv
vs move
thing?
@anmonteiro it actually was the source of the issue. I thought that was some post-build cleanup stuff, turns out I was at halftime 馃槷
@moxaj does changing mv
to move
make your build succeed?
were you building on PowerShell or cmd?
interesting
@moxaj last question (I鈥檓 not familiar with Windows, sorry!): does move
work in Powershell?
weird
CI is running in cmd
and the builds have been passing
I鈥檒l take your PR in any case, if CI succeeds
Appveyor has a 90 minutes timeout
I managed to increase it from 60 a while ago
the other 2 take like ~10 minutes, they probably cache some artifacts, is that not possible with appveyor?
it is
cache must be broken
since the Node 8.0 upgrade
in any case it鈥檒l take 40 minutes with cache 馃槥
yeah I think the cache is broken