You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Action.yml files specifies that a cxcli variable is exported and contains the scan's outputs, but this appear to not be the case.
Expected behavior
Referencing the cxcli output from a subsequent steps should yield the scan's outputs. For example, a steps referencing a scan with the id set asscan like this should print the outputs:
- name: Save relevant summary to cx_result.mdrun: echo "${{ steps.scan.outputs.cxcli }}"
Actual behavior
Using above steps yields an empty string.
Steps to reproduce
Have a github actions file launch a scans.
Add an id: something to the steps calling this action
In a subsequent steps, reference the output variables cxcli like so:
- name: Save relevant summary to cx_result.mdrun: echo "${{ steps.scan.outputs.cxcli }}"
Additional comments
We're trying to read the text output from the scan. We have resorted to using the output.log file that is created instead
I just needed the cxoutput; reading the output.log file solved the issue, but it is confusing that the cxcli output is defined in action.yml but does not contain anything
Describe the bug
The Action.yml files specifies that a cxcli variable is exported and contains the scan's outputs, but this appear to not be the case.
Expected behavior
Referencing the
cxcli
output from a subsequent steps should yield the scan's outputs. For example, a steps referencing a scan with the id set asscan
like this should print the outputs:Actual behavior
Using above steps yields an empty string.
Steps to reproduce
id: something
to the steps calling this actionAdditional comments
We're trying to read the text output from the scan. We have resorted to using the output.log file that is created instead
Logs
Using this workflow:
The text was updated successfully, but these errors were encountered: