foo-software / lighthouse-check-action

GitHub Action for running @GoogleChromeLabs Lighthouse audits with all the bells and whistles 🔔 Multiple audits, Slack notifications, and more!
https://github.com/marketplace/actions/lighthouse-check
MIT License
478 stars 24 forks source link

mkdir: cannot create directory ‘/tmp/artifacts’: File exists #63

Closed willpaige closed 2 years ago

willpaige commented 2 years ago

Hi,

My action keeps failing with the below: Screenshot 2021-10-15 at 12 08 30 pm

Setup:

lighthouse-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@master
      - run: mkdir /tmp/artifacts
      - name: Run Lighthouse
        uses: foo-software/lighthouse-check-action@master
        with:
          apiToken: ${{ secrets.FOO_ACCESS_TOKEN }}
          author: ${{ github.actor }}
          awsAccessKeyId: ${{ secrets.AWS_ACCESS_KEY_ID }}
          awsBucket: ${{ secrets.STAGING_LIGHTHOUSE_S3_BUCKET_ARN }}
          awsRegion: ${{ secrets.AWS_ENG_TEST_REGION }}
          awsSecretAccessKey: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          branch: ${{ github.ref }}
          outputDirectory: /tmp/artifacts
          urls: 'https://www.website.com'
          sha: ${{ github.sha }}
          slackWebhookUrl: ${{ secrets.WORDPRESS_SLACK_URL }}
      - name: Upload artifacts
        uses: actions/upload-artifact@master
        with:
          name: Lighthouse reports
          path: /tmp/artifacts
adamhenson commented 2 years ago

Hi. The error says that /tmp/artifacts directory exists.

Did you try removing the line below?

- run: mkdir /tmp/artifacts
willpaige commented 2 years ago

Ugh, that makes sense. Thanks.

adamhenson commented 2 years ago

It’s still odd @willpaige. Does that directory exist in your code? If not, I should try to reproduce and update the docs if needed. The only thing I can think of is maybe actions/upload-artifact changed recently.