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
Recent changes are causing an error in GitHub Actions. See output from workflow below:
Run ts-graphviz/setup-graphviz@v2
with:
ubuntu-skip-apt-update: false
macos-skip-brew-update: false
env:
pythonLocation: /opt/hostedtoolcache/Python/3.11.9/x64
PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig
Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.9/x64
Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.9/x64
Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.9/x64
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.9/x64/lib
/usr/bin/sudo apt-get clean
/usr/bin/sudo sudo rm /etc/apt/sources.list.d/microsoft-prod.list
root is not in the sudoers file. This incident will be reported.
Error: The process '/usr/bin/sudo' failed with exit code 1
Workflow fails at this step.
To Reproduce
Steps to reproduce the behavior:
Use in a GitHub Action workflow like below:
Graphviz should install. I have verified this works if changing the version to v2.0.0 instead of v2.
Additional context
I have also verified that the updated version v2.0.1 works on GitHub hosted runners. However, we are using self-hosted runners. Our solution may be pinning the action to v2.0.0. Not sure if self-hosted runners are used to test changes for this action, but consider that.
The text was updated successfully, but these errors were encountered:
Describe the bug
Recent changes are causing an error in GitHub Actions. See output from workflow below:
Workflow fails at this step.
To Reproduce
Steps to reproduce the behavior:
Use in a GitHub Action workflow like below:
Expected behavior
Graphviz should install. I have verified this works if changing the version to
v2.0.0
instead ofv2
.Additional context
I have also verified that the updated version
v2.0.1
works on GitHub hosted runners. However, we are using self-hosted runners. Our solution may be pinning the action tov2.0.0
. Not sure if self-hosted runners are used to test changes for this action, but consider that.The text was updated successfully, but these errors were encountered: