setup-ffmpeg: Fetching versions list fails sometime

Hi, I am using this action in a repo where 8 jobs starts simultaneously and in some cases It throws fetch failed error. This error doesn’t occur in v2

image

About this issue

  • Original URL
  • State: open
  • Created 5 months ago
  • Reactions: 9
  • Comments: 15 (4 by maintainers)

Commits related to this issue

Most upvoted comments

I end up creating a composite github action:

name: 'Setup FFmpeg with retries'
description: 'Installs FFmpeg with retry logic'
inputs:
  github-token:
    description: 'GitHub Token (required by "FedericoCarboni/setup-ffmpeg@v3")'
    required: true

runs:
  using: 'composite'
  steps:
    - name: Setup FFmpeg
      id: attempt1
      continue-on-error: true
      uses: FedericoCarboni/setup-ffmpeg@v3
      with:
        github-token: ${{ inputs.github-token }}

    - name: Setup FFmpeg (retry 2)
      if: ${{ steps.attempt1.outcome == 'failure' }}
      id: attempt2
      continue-on-error: true
      uses: FedericoCarboni/setup-ffmpeg@v3
      with:
        github-token: ${{ inputs.github-token }}

    - name: Setup FFmpeg (retry 3)
      if: ${{ steps.attempt2.outcome == 'failure' }}
      id: attempt3
      continue-on-error: true
      uses: FedericoCarboni/setup-ffmpeg@v3
      with:
        github-token: ${{ inputs.github-token }}

This file is saved in my repo under actions/setup-ffmpeg/action.yaml.

The I changed my workflow to call

      - uses: actions/checkout@v2
      - name: Setup FFmpeg (with retries)
        uses: ./actions/setup-ffmpeg
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}

instead of the original action. Hopefully, that would do the trick.

For anyone annoyed by this issue – while I try to understand why a GitHub runner would have network errors – pinning ffmpeg to a specific version should mitigate it, set ffmpeg-version to 6.1.0 for example.

Adding a +1 and reporting this is still occurring on v3 on the ubuntu-latest github runners.

Screenshot 2024-03-19 at 13 41 45

I have registered a job that runs once an hour, but since v3, it has failed once a day, every 24 times.