No error information on invalid working directory #387

New Issue

hakito · 2023-10-25T07:46:17Z

hakito commented

2023-10-25 07:46:17 +00:00

When specifiying a working directory that does not exist, the step fails without any indication of the underlying error in the web interface:

name: Sample
on: [push]

jobs:  
  Fail:
    runs-on: windows
    steps:
        - run: echo "Hello directory"
          working-directory: DoesNotExist

Only the output in the console of the act runner gives the hint for the error:

[Sample/Fail] [DEBUG] Failed to setup Pty Unsupported
[Sample/Fail] ❌ Failure - Main echo "Hello directory"
[Sample/Fail] fork/exec C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe: The directory name is invalid.

Proposal: Forward all error information to the web ui.

When specifiying a working directory that does not exist, the step fails without any indication of the underlying error in the web interface: ```yaml name: Sample on: [push] jobs: Fail: runs-on: windows steps: - run: echo "Hello directory" working-directory: DoesNotExist ``` Only the output in the console of the act runner gives the hint for the error: > [Sample/Fail] [DEBUG] Failed to setup Pty Unsupported > [Sample/Fail] ❌ Failure - Main echo "Hello directory" > [Sample/Fail] fork/exec C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe: The directory name is invalid. **Proposal**: Forward all error information to the web ui.

lunny added the

kind

bug

label 2023-10-27 06:41:47 +00:00

Zettat123 commented

2024-03-06 08:42:58 +00:00

Tested the workflow and found the error information in Complete job section

Tested the workflow and found the error information in `Complete job` section <img src="/attachments/b6a50111-b53a-42c2-ad28-aaaa6e8d1a23" width="640px"/>

image.png

19 KiB

hakito commented

2024-03-06 10:21:31 +00:00

At least the error info is there. But its a bit counter intuitive dont you think?

Sign in to join this conversation.

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/act_runner#387