-
Notifications
You must be signed in to change notification settings - Fork 764
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
Error: Unrecognized if-no-files-found input. Provided: . Available options: warn,error,ignore #255
Comments
I'm also facing the same issue |
We have similar issue, but as warning and looks like this "if-no-files-found" isn't working.
|
I just want to add.. I'm experiencing this same issue. Also on a self-hosted linux based runner. edit: update.. oddly enough, the upload succeeds! Despite the error. Edit: Forked the main branch to try a test.
|
We are also experiencing this issue. Our configuration looks like the following: - uses: actions/upload-artifact@v3
with:
name: <artifact-name>
path: |
path/to/file1
path/to/file2
path/to/file3 and exactly the below error is printed once this action runs:
I have tried the below configuration too, with the same error message. - uses: actions/upload-artifact@v3
with:
name: <artifact-name>
path: |
path/to/file1
path/to/file2
path/to/file3
if-no-files-found: warn The odd thing is, the upload of files succeed. The problem is that this workflow looks to be failed because of this |
having the same issue, is there a fix ? |
same here! |
ain't this a beauty, I am already tired of countless github actions issues we are facing :) I hope it's the last time I ever use it. |
Describe the bug
I'm running a self hosted runner and the workflow job is ran in a container. When a test fails and should upload the screenshots, the following error is displayed. As seen in screenshot below, I have set the
if-no-files-found
toignore
, but error still displays as if this was configured incorrectly.Version
Environment
Screenshots
The displayed error message:
The start of the workflow:
If you require more info, let me know.
The text was updated successfully, but these errors were encountered: