Fork me on GitHub
#graalvm
<
2022-09-18
>
ericdallo16:09:35

I'm giving a try on Oracle Cloud free tier, which allows you have a instance and configure github self runner for that, then we may have aarch64 builds entirely on github actions

borkdude16:09:57

only for linux right

ericdallo16:09:21

Hum, good point, I didn't see anything about mac, will take a look

ericdallo16:09:34

I didn't setup yet

borkdude16:09:58

Spoiler: it does not support mac

ericdallo16:09:05

yeah, it seems 😔

ericdallo16:09:33

I applied clojure-lsp for https://www.macstadium.com/opensource-application, not sure if they will accept, but worth the try :)

borkdude16:09:22

You already are using CirrusCI, but they don't support Github self-hosted hooks right?

borkdude16:09:29

Is that why you are looking at MacStadium?

ericdallo16:09:28

yeah, I'm having some race conditions issues where cirrus builds before github action and publish to a wrong clojure-lsp dev release, I could try trigger the cirrus CI build via API in the future

borkdude16:09:06

I have solved this problem by using my own library which uploads to Github releases in an idempotent way

borkdude16:09:15

wait, I think you're already using that

borkdude16:09:49

but maybe the problem is that you're using a very fine-grained version number with milliseconds in it

ericdallo16:09:59

yep, not milliseconds, but https://github.com/clojure-lsp/clojure-lsp/blob/master/scripts/clojure_lsp/release_artifact.clj#L25 is the issue, we expect the release dev tag was already built

borkdude16:09:58

maybe you should let the creation of the tag initiate the action, not the other way around?

ericdallo17:09:52

yeah, and move the cirrus build to the dev release repo right? because the dev tag is created there