I have some problems with karma on circle-ci 😕 some tests just fail, rerunning them succeeds https://circleci.com/gh/heyarne/airsonic-ui/32

with "some tests" i mean some test runs, not some tests out of the whole test suite

language is hard

https://circleci.com/gh/heyarne/airsonic-ui/33 is the same code, just rebuilt

FWIW I've been using karma tests on circle-ci for a month or so now and had no issues

here's my karma.conf.js: https://github.com/Lokeh/hx/blob/master/karma.conf.js

@lilactown do you use it locally, too?

nope. I use the graphical test runner

Because I've been using it in the background to continuously watch and build

Graphical test runner?

https://shadow-cljs.github.io/docs/UsersGuide.html#target-browser-test

Ah

@arne-clojurians it seems like compilation didn't finish before the tests are run

shadow-cljs - config: /home/circleci/repo/shadow-cljs.edn  cli version: 2.8.25  node: v10.15.3
shadow-cljs - updating dependencies
shadow-cljs - dependencies updated
[:test] Compiling ...

> [email protected] test:run /home/circleci/repo
> karma start --single-run

there have been issues before with circleci killing build processes running OOM. not sure how big your build is but it seems to help to set :jvm-opts ["-Xmx2G"] (limiting the JVM to max 2gig ram)

Hm I might just dump karma altogether. Or run a config similar to lilactown's. As much as I like having the tests run in the background permanently it's also quite fragile with complaining about syntax errors every so often yada yada

The browser-test might serve me just as well. 🙂

there are no syntax errors

Plus if there are any contributors I don't have to tell them to install chrome

Not on circleci, no

it just isn't finished compiling. figure out why and the problem goes away

But with the --watch feature

ah ok

ooh wow stackoverflow sure is pretty today

i already forgot about that font, it used to be everywhere for a time