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

Summary export permission denied #1

Closed
edno opened this issue Dec 16, 2020 · 5 comments
Closed

Summary export permission denied #1

edno opened this issue Dec 16, 2020 · 5 comments
Assignees

Comments

@edno
Copy link

edno commented Dec 16, 2020

When passing the flag --summary-export results.json then an error is raised:

level=error msg="failed to create summary export file" error="open results.json: permission denied"

The result is that no summary file is created.

Example of step:

uses: k6io/action@v0.1
with:
  filename: scenarios/${{ github.event.inputs.scenario }}.js
  flags: --summary-export ${{ github.event.inputs.scenario }}.results.json

The expected result is that the flag works like on a local environment, and the result.json file is created and can further be exported using actions/download-artifact@v2

uses: actions/upload-artifact@v2
with:
  name: ${{ github.event.inputs.scenario }}.results.json
  path: ${{ github.event.inputs.scenario }}.results.json
@edno
Copy link
Author

edno commented Dec 21, 2020

A possible root cause is that the k6 docker image set the USER in the Dockerfile, what is not recommended as per Github Action documentation.

@simskij
Copy link
Contributor

simskij commented Dec 21, 2020

Hey,

Thank you for your report! I'll have a look at this. Contrary to GitHub's own recommendation, it's generally a bad practice to run anything in docker as root. I'll get back to you once I have more details.

Best,
Simme

@simskij simskij self-assigned this Dec 21, 2020
@edno
Copy link
Author

edno commented Jan 5, 2021

Happy New Year @simskij

Any update on this issue?

If you have any suggestion for a workaround, I'll be happy to give it a try.

@simskij
Copy link
Contributor

simskij commented Jan 19, 2021

Hi @edno,

This should be fixed as of v0.2.0, which I just released.

Best,
Simme

@simskij simskij closed this as completed Jan 19, 2021
@edno
Copy link
Author

edno commented Jan 20, 2021

Confirmed. It works as expected 😃

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

No branches or pull requests

2 participants