@glenjamin > I’ll check next week. which org/project is this? Thanks, I'll be looking forward to trying out arm

aha, the flag we've set on your org is clashing with a project-level flag. We're just figuring out the best to resolve these - i'll let you know when it's sorted

@borkdude should be sorted now

@glenjamin :thumbsup: Should I try arm.medium, arm.large or both?

either should work

Seems to work now, thanks!!

nice!

did you already have steps you know worked? sub 30 minutes from access to working is great

@glenjamin I could just re-use my linux job

GraalVM has aarch64 so I just had to rename amd64 to aarch64 basically

ah nice, were you already using machine executor for linux?

no, but this was easy enough to find out using these docs: https://github.com/CircleCI-Public/arm-preview-docs/blob/main/README.md

I am using machine also for macos btw

no I'm not

anyway, it was a small change

linux:
    docker:
      - image: circleci/clojure:lein-2.9.1
    working_directory: ~/repo
    environment:
    ...
    resource_class: large

linux-aarch64:
    machine:
      enabled: true
      image: ubuntu-2004:202101-01
    resource_class: arm.large
    working_directory: ~/repo
    environment:
    ...

ah cool, and the preinstalled jvm was suitable already

@glenjamin I'm not using the preinstalled one, I download graalvm already in the linux build and now also in the linux-aarch64 build:

- run:
          name: Download GraalVM
          command: |
            cd ~
            if ! [ -d graalvm-ce-java11-21.0.0 ]; then
              curl -O -sL 
              tar xzf graalvm-ce-java11-linux-aarch64-21.0.0.tar.gz
            fi

I also install clojure and leiningen myself, I basically don't care about the base image for this particular project at all as long as it's linux (or mac) and has enough memory ;)