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
Hi, I am trying use this setup-xvfb action for a Python Qt project I am developing and I get "Aborted (core dumped)". I reduced my setup to a minimal example, see https://github.com/hakonhagland/pytest-xvfb-test, and this github action job log:
[...]
File "/opt/hostedtoolcache/Python/3.10.12/x64/lib/python3.10/runpy.py", line 86 in _run_code
File "/opt/hostedtoolcache/Python/3.10.12/x64/lib/python3.10/runpy.py", line 196 in _run_module_as_main
Extension modules: PyQt6.QtCore, PyQt6.QtGui, PyQt6.QtWidgets, PyQt6.QtTest (total: 4)
Aborted (core dumped)
/usr/bin/bash /home/runner/work/_actions/coactions/setup-xvfb/v1/dist/cleanup.sh
/usr/bin/bash: /home/runner/work/_actions/coactions/setup-xvfb/v1/dist/cleanup.sh: No such file or directory
Error: The process '/usr/bin/xvfb-run' failed with exit code 134
The workflow step that triggers the issue is like this:
- name: Run unit tests
uses: coactions/setup-xvfb@v1
with:
run: |
poetry run python -m pytest
Any ideas what could be wrong?
The text was updated successfully, but these errors were encountered:
rnorris
added a commit
to rnorris/viking
that referenced
this issue
Aug 18, 2023
Fix outdated Github base Ubuntu image vs server package versions
(need to update before installing)
Use xvfb in build and test pipelines so DISPLAY dependent tests can be run
NB coactions xvfb broken ATM see:
coactions/setup-xvfb#19
Hi, I am trying use this
setup-xvfb
action for a Python Qt project I am developing and I get "Aborted (core dumped)". I reduced my setup to a minimal example, see https://github.com/hakonhagland/pytest-xvfb-test, and this github action job log:https://github.com/hakonhagland/pytest-xvfb-test/actions/runs/5626878877/job/15248519431
The workflow step that triggers the issue is like this:
Any ideas what could be wrong?
The text was updated successfully, but these errors were encountered: