Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random package install failures in MacOS CI actions #400

Closed
mooreryan opened this issue Jan 21, 2022 · 5 comments
Closed

Random package install failures in MacOS CI actions #400

mooreryan opened this issue Jan 21, 2022 · 5 comments
Labels

Comments

@mooreryan
Copy link

So I know this won't be a very useful issue description, but on multiple actions across multiple repositories, I will randomly get failures on the MacOS.

For example, I will have a step in the action like this...

opam exec -- opam install . --jobs 1 --deps-only --with-doc --with-test

And there will often be a random package install failure e.g.,

┌─ The following actions failed
│ λ build ppxlib 0.24.0
└─ 

Generally it will be a different package that will fail to install each time the action is run. Often, if I rerun the action once or twice it will clear up any problems.

I'm having trouble reproducing this issue as the same action will be totally fine for many commits/runs and then it will randomly fail a couple of times, then be totally fine for the next few runs.

I'm wondering if anyone else has run into this and if so, is there a way to fix it other than just re-running failed actions?

@smorimoto
Copy link
Member

Maybe you are enabling the dune cache? The current dune 2 is buggy with the dune cache, which is completely fixed in the upcoming dune 3, and that's why we don't enable the dune cache by default at the moment.

@smorimoto smorimoto pinned this issue Jan 22, 2022
@mooreryan
Copy link
Author

Thanks, I will take a look at that and report back!

@smorimoto
Copy link
Member

Resolved with ocaml/opam-repository#20758.

@smorimoto smorimoto unpinned this issue Mar 1, 2022
@mooreryan
Copy link
Author

mooreryan commented Dec 2, 2022

I'm not sure this issue is actually resolved. When using macOS actions, I still get similar problems unless I set dune-cache: false. Note that I'm using the v2 of the setup-ocaml action, and the project is using dune 3.5.

(Edit: just to be clear, when I use dune-cache: false, it does when using macOS, but using dune-cache: true gives the same type of errors.)

Edit 2: Setting dune-cache: false when running on macOS resolves the problem. If dune-cache: true on macOS, then the problem still exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants