-
Notifications
You must be signed in to change notification settings - Fork 83
Open
Description
Sometimes I am seeing the following error, sometimes not. I believe this happens when I am running multiple steps in parallel. How would I go about fixing this?
Run android-actions/setup-android@v[2](https://github.com/ShareTheMeal/app-android/runs/5864050026?check_suite_focus=true#step:4:2)
env:
JAVA_HOME: /home/actions-runner/_work/_tool/Java_Zulu_jdk/11.0.14-9/x64
(node:[3](https://github.com/ShareTheMeal/app-android/runs/5864050026?check_suite_focus=true#step:4:3)061[4](https://github.com/ShareTheMeal/app-android/runs/5864050026?check_suite_focus=true#step:4:4)) UnhandledPromiseRejectionWarning: Error: Unable to locate executable file: unzip. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
at Object.<anonymous> (/home/actions-runner/_work/_actions/android-actions/setup-android/v2/dist/index.js:2117:27)
at Generator.next (<anonymous>)
at fulfilled (/home/actions-runner/_work/_actions/android-actions/setup-android/v2/dist/index.js:1942:[5](https://github.com/ShareTheMeal/app-android/runs/5864050026?check_suite_focus=true#step:4:5)8)
(node:30[6](https://github.com/ShareTheMeal/app-android/runs/5864050026?check_suite_focus=true#step:4:6)14) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:30614) [DEP001[8](https://github.com/ShareTheMeal/app-android/runs/5864050026?check_suite_focus=true#step:4:8)] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Also it looks like this action is not terminating correctly so it looks like the steps after this one fail.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
