Fork me on GitHub
#cljs-dev
<
2023-04-06
>
borkdude15:04:10

Seems one CI step had a network hiccup

dnolen17:04:43

hrm wasn’t fixed by re-running, I wonder if something is up w/ a dep

borkdude11:04:58

FWIW the tests run fine locally

clojure -M:compiler.test:compiler.test.run
Ran 213 tests containing 920 assertions.
0 failures, 0 errors.

borkdude18:04:06

I think it's just a network hiccup, given:

npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

borkdude18:04:20

Maybe re-trigger it a few more times?

dnolen12:04:12

trying it again

borkdude12:04:58

@U050B88UR When is CLJS due for another release? Some people will run into the above issue with vanilla CLJS (but not with shadow-cljs): https://github.com/metosin/malli/pull/888#issuecomment-1503249983