This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-07
Channels
- # announcements (27)
- # babashka (29)
- # beginners (280)
- # calva (34)
- # cider (4)
- # circleci (11)
- # cljfx (10)
- # cljsrn (1)
- # clojure (526)
- # clojure-dev (9)
- # clojure-europe (42)
- # clojure-finland (5)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-taiwan (2)
- # clojure-uk (14)
- # clojurescript (40)
- # clr (43)
- # community-development (5)
- # css (4)
- # cursive (7)
- # duct (82)
- # events (1)
- # fulcro (72)
- # garden (44)
- # hoplon (3)
- # java (40)
- # jobs (4)
- # juxt (1)
- # luminus (53)
- # meander (13)
- # off-topic (26)
- # pathom (14)
- # pedestal (3)
- # portal (2)
- # rdf (3)
- # re-frame (54)
- # releases (10)
- # remote-jobs (3)
- # sci (74)
- # shadow-cljs (47)
- # startup-in-a-month (5)
- # testing (9)
- # tools-deps (73)
- # vim (12)
What space do you get in circleci builds? > /usr/bin/ld: final link failed: No space left on device
Is there a good way to run a benchmark during CI on circleci? For Datahike we could use an instance that has a certain performance consistency to run a benchmark on.
https://circleci.com/docs/2.0/runner-overview/ is the only way I know of currently to run a CircleCI job on bare metal.
๐ 3
@timok using the machine executor is (currently) equivalent to getting an n2 instance on GCP, and will always be a dedicated VM
the docker executor runs on a multi-tenant system, but we donโt overprovision, so in theory it should be fairly consistent. In practice this varies