Skip to content

Investigation framework and completed playbooks integration. Closes #173 #362

Investigation framework and completed playbooks integration. Closes #173

Investigation framework and completed playbooks integration. Closes #173 #362

Triggered via pull request November 14, 2024 11:59
Status Failure
Total duration 55s
Artifacts

pull_request_automation.yml

on: pull_request
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 6 warnings
tests (3.9)
InvocationError for command /home/runner/work/pyintelowl/pyintelowl/.tox/py39-click7/bin/coverage run -m unittest discover tests (exited with code 1)
tests (3.9)
InvocationError for command /home/runner/work/pyintelowl/pyintelowl/.tox/py39-click8/bin/coverage run -m unittest discover tests (exited with code 1)
tests (3.9)
py39-click7: commands failed
tests (3.9)
py39-click8: commands failed
tests (3.9)
Process completed with exit code 1.
tests (3.11)
InvocationError for command /home/runner/work/pyintelowl/pyintelowl/.tox/py311-click7/bin/coverage run -m unittest discover tests (exited with code 1)
tests (3.11)
InvocationError for command /home/runner/work/pyintelowl/pyintelowl/.tox/py311-click8/bin/coverage run -m unittest discover tests (exited with code 1)
tests (3.11)
py311-click7: commands failed
tests (3.11)
py311-click8: commands failed
tests (3.11)
Process completed with exit code 1.
tests (3.10)
InvocationError for command /home/runner/work/pyintelowl/pyintelowl/.tox/py310-click7/bin/coverage run -m unittest discover tests (exited with code 1)
tests (3.10)
InvocationError for command /home/runner/work/pyintelowl/pyintelowl/.tox/py310-click8/bin/coverage run -m unittest discover tests (exited with code 1)
tests (3.10)
py310-click7: commands failed
tests (3.10)
py310-click8: commands failed
tests (3.10)
Process completed with exit code 1.
tests (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
tests (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
tests (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
tests (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
tests (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
tests (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/