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
471 stars 24 forks source link

mkdir: cannot create directory Error is Visible #104

Closed Mitesh411 closed 1 year ago

Mitesh411 commented 1 year ago

Describe the bug Implemented below .yml File but Failed in Pipeline

`name: Lighthouse on: [pull_request]

jobs: lighthouse: runs-on: ubuntu-latest steps:

To Reproduce Please Do Navigate the Link:- https://github.com/Mitesh411/Lighthouse-Demo/blob/main/.github/workflows/blank.yml

Expected behavior The folder should be created in /tmp/artifacts

Additional context Screen short are attached screenshot-github com-2022 08 11-09_40_04 screenshot-github com-2022 08 11-09_39_38

adamhenson commented 1 year ago

Hi @Mitesh411 - this isn't related to Lighthouse Check GitHub action as I can see the failure occurs before the Lighthouse Check. Although we are using it in our documentation, so I'm hoping the below will help.

The error is occurring in the mkdir command within the ubuntu-latest container. Though it's not related to Lighthouse Check - I am curious why this issue is happening as it didn't happen in the past. Perhaps the tmp directory existed in older GitHub Runners and does not in more current versions.

Please try the below command instead (to use -p which will create any subdirectories):

mkdir -p ${{ github.workspace }}/tmp/artifacts

I think the above will work and since this issue isn't directly related to Lighthouse Check - I'm closing this issue. But please do confirm here that the above works (or doesn't). I'll also update our documentation to reflect the above.

adamhenson commented 1 year ago

Updated the documentation.

Mitesh411 commented 1 year ago

It is now Working @adamhenson Thank you for helping me out

mkdir -p is working

adamhenson commented 1 year ago

Glad it worked and thanks for opening the issue. Our docs should have good examples, so sooty for the confusion and glad we got to the bottom of it.