# Running CI for Julia 1.6 on Github MacOS runners seems to fail?

**URL:** https://discourse.julialang.org/t/running-ci-for-julia-1-6-on-github-macos-runners-seems-to-fail/116577
**Category:** General Usage
**Created:** [July 3, 2024, 8:56am UTC](https://discourse.julialang.org/t/running-ci-for-julia-1-6-on-github-macos-runners-seems-to-fail/116577 "2024-07-03T08:56:45Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![vettert](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vettert/32/30599_2.png) [@vettert](https://discourse.julialang.org/u/vettert)
#### Post date: [July 3, 2024, 8:56am UTC](https://discourse.julialang.org/t/running-ci-for-julia-1-6-on-github-macos-runners-seems-to-fail/116577/1 "2024-07-03T08:56:45Z")

</div>

I am trying to get tests for a package to pass on Julia 1.6 and different OS.  
Here is my CI file: [Open62541.jl/.github/workflows/CI.yml at main · martinkosch/Open62541.jl](https://github.com/martinkosch/Open62541.jl/blob/main/.github/workflows/CI.yml)

Things are going fine, except for MacOS X, which fails with the following (not very explanatory message):

 ![image](https://global.discourse-cdn.com/julialang/original/3X/c/3/c31fdf6b6ba43fb3a2bd396b44c71532753944b2.png)

Does it mean that there is no Julia 1.6 version (anymore?) on mac os github runners that run on ARM64 architecture? Is this what the error message is trying to tell me?

Of course, any suggestions on how to “fix” my CI file would be also most welcome!

---

<div class="post-metadata">

### Author: ![jmair](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmair/32/35117_2.png) [@jmair](https://discourse.julialang.org/u/jmair)
#### Post date: [July 3, 2024, 9:38am UTC](https://discourse.julialang.org/t/running-ci-for-julia-1-6-on-github-macos-runners-seems-to-fail/116577/2 "2024-07-03T09:38:42Z")

</div>

In the CI for one of our packages, we’ve been using v1 for the setup-julia action and it passes that stage of the CI so you could try switching from v2 to v1 (should be easy to change in the CI.yml file).

This should come with a caveat that we’ve been having issues with the GitHub actions MacOS runners as well, just later on in the CI process, but this is likely related directly to our package.

---

<div class="post-metadata">

### Author: ![vettert](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vettert/32/30599_2.png) [@vettert](https://discourse.julialang.org/u/vettert)
#### Post date: [July 3, 2024, 9:41am UTC](https://discourse.julialang.org/t/running-ci-for-julia-1-6-on-github-macos-runners-seems-to-fail/116577/3 "2024-07-03T09:41:06Z")

</div>

Thanks jmair.

I dug a little more around and it seems that this is a known issue:  
[Failed without logs on MacOS Julia 1.6 · Issue #240 · julia-actions/setup-julia (github.com)](https://github.com/julia-actions/setup-julia/issues/240)

---

<div class="post-metadata">

### Author: ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [July 3, 2024, 10:03am UTC](https://discourse.julialang.org/t/running-ci-for-julia-1-6-on-github-macos-runners-seems-to-fail/116577/4 "2024-07-03T10:03:54Z")

</div>

> [@vettert](#):
>
> Does it mean that there is no Julia 1.6 version (anymore?) on mac os github runners that run on ARM64 architecture?

There never was.

> [@jmair](#):
>
> we’ve been using v1 for the setup-julia action and it passes that stage of the CI so you could try switching from v2 to v1 (should be easy to change in the CI.yml file).

This has nothing to do with setup-julia v1 vs v2.

> [@vettert](#):
>
> Of course, any suggestions on how to “fix” my CI file would be also most welcome!

You have some options:

- always [force using the x64 build of Julia](https://github.com/julia-actions/setup-julia/blob/4778d3d0c86f8c23cee389c7814186bf6b9e5aad/README.md#inputs) (`with: arch: x64`)
- don’t run macOS tests on 1.6 with aarch64 architecture
- don’t use `macos-latest` (which means `macos-14`, which is Apple Silicon only) and instead use `macos-13`, which runs on native Intel CPUs. This will probably stop working at some point in the future.
