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

Flaky Installer issues #306

Open
isaacsanders opened this issue Oct 16, 2024 · 3 comments
Open

Flaky Installer issues #306

isaacsanders opened this issue Oct 16, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@isaacsanders
Copy link

isaacsanders commented Oct 16, 2024

The bug

The tool cache install fails

Software versions

A list of software versions where the bug is apparent, as detailed as possible:

  • setup-beam: 1.18.1
  • otp-version: 25
  • elixir-version: 1.16.3

How to replicate

An ordered list of steps to replicate the bug:

Invoke a workflow using the action similarly to the following:

      - name: Set up Elixir
        uses: erlef/setup-beam@b9c58b0450cd832ccdb3c17cc156a47065d2114f # v1.18.1
        with:
          otp-version: "25"
          elixir-version: "1.16.3"

This won't always fail, but it fails often enough to raise concerns.

Expected behaviour

The versions should be installed and interact with the GHA cache normally.

Additional context

GHES 3.10

This is the error I'm seeing:

Action install Erlang/OTP OTP-25.3.2.13 failed for mirror https://builds.hex.pm/, with Error: File was unable to be removed Error: ENOTEMPTY: directory not empty, rmdir '/opt/hostedtoolcache/otp/ubuntu-22.04/OTP-25.3.2.13/x64/lib'
@isaacsanders isaacsanders added the bug Something isn't working label Oct 16, 2024
@isaacsanders isaacsanders changed the title Flaky Installer around Versioning and Cache issues Flaky Installer issues Oct 16, 2024
@paulo-ferraz-oliveira
Copy link
Collaborator

Hi. Thanks for the report.

I've seen that happen with other actions/contexts, so always assumed it was a GitHub Actions -specific issue, where they seem to be reusing the same container (?)

I'll leave this open in case someone else has input, but I don't think we ever try to remove our installed elements, or cache over them...

@isaacsanders
Copy link
Author

I can post a stack trace. It does happen in the code

@paulo-ferraz-oliveira
Copy link
Collaborator

I can imagine it happen in the code, but we mean the action's code or some dependency?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants