Support 24.04 #328
Triggered via pull request
January 29, 2025 22:04
Status
Cancelled
Total duration
47m 56s
Artifacts
–
tests.yml
on: pull_request
changed_states
2s
Matrix: test_states
Annotations
40 errors and 7 warnings
test_states (3007, 22.04, sift.python3-packages.analyzemft)
The operation was canceled.
|
test_states (3007, 22.04, sift.python3-packages.analyzemft)
The file '/home/runner/runners/2.321.0/_diag/pages/108b07dc-8b82-4580-8724-42656ac83554_bc84511b-ed6f-5e5e-74d6-1a459eaca898_1.log' already exists.
|
test_states (3007, 24.04, sift.packages.libpff)
Value cannot be null. (Parameter 'network')
|
test_states (3007, 24.04, sift.packages.libpff)
The operation was canceled.
|
test_states (3007, 22.04, sift.scripts.docker-compose)
The file '/home/runner/runners/2.321.0/_diag/pages/108b07dc-8b82-4580-8724-42656ac83554_70515be2-21db-5cd5-3c76-76c328937a8f_1.log' already exists.
|
test_states (3007, 22.04, sift.scripts.docker-compose)
The operation was canceled.
|
test_states (3007, 22.04, sift.scripts.docker-compose)
The file '/home/runner/runners/2.321.0/_diag/pages/108b07dc-8b82-4580-8724-42656ac83554_70515be2-21db-5cd5-3c76-76c328937a8f_1.log' already exists.
|
test_states (3007, 24.04, sift.packages.pff-tools)
The file '/home/runner/runners/2.321.0/_diag/pages/108b07dc-8b82-4580-8724-42656ac83554_aa4f4774-da8d-5fe6-2bdc-e32df5692196_1.log' already exists.
|
test_states (3007, 24.04, sift.packages.pff-tools)
The operation was canceled.
|
test_states (3007, 24.04, sift.packages.libafflib)
The operation was canceled.
|
test_states (3007, 24.04, sift.packages.libafflib)
The file '/home/runner/runners/2.321.0/_diag/pages/108b07dc-8b82-4580-8724-42656ac83554_5c5b8cfb-54c9-5d7a-8cf3-89f9e60dce53_1.log' already exists.
|
test_states (3007, 24.04, sift.packages.libafflib)
Missing file at path: /__w/_temp/_runner_file_commands/set_output_fcbd4181-5f7b-48d4-a09a-7c532195c7dc
|
test_states (3007, 24.04, sift.packages.libafflib)
The file '/home/runner/runners/2.321.0/_diag/pages/108b07dc-8b82-4580-8724-42656ac83554_5c5b8cfb-54c9-5d7a-8cf3-89f9e60dce53_1.log' already exists.
|
test_states (3007, 24.04, sift.python3-packages.python-evtx)
The operation was canceled.
|
test_states (3007, 24.04, sift.scripts.docker-compose)
The file '/home/runner/runners/2.321.0/_diag/pages/108b07dc-8b82-4580-8724-42656ac83554_f11e24db-71ec-5633-dca4-f3f85b087700_1.log' already exists.
|
test_states (3007, 24.04, sift.scripts.docker-compose)
The operation was canceled.
|
test_states (3007, 24.04, sift.repos.dotnet-backports)
The operation was canceled.
|
test_states (3007, 22.04, sift.scripts.amcache)
The operation was canceled.
|
test_states (3007, 24.04, sift.packages.python3-magic)
The hosted runner: GitHub Actions 15 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 22.04, sift.scripts.packerid)
The hosted runner: GitHub Actions 17 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.defang)
The hosted runner: GitHub Actions 35 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.windowsprefetch)
The hosted runner: GitHub Actions 58 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.scripts.zimmerman)
The hosted runner: GitHub Actions 59 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.usnparser)
The hosted runner: GitHub Actions 67 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.mac-apt)
The hosted runner: GitHub Actions 80 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.hindsight)
The hosted runner: GitHub Actions 102 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.ioc-writer)
The hosted runner: GitHub Actions 122 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.sqlite-carver)
The hosted runner: GitHub Actions 126 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 22.04, sift.repos.dotnet-backports)
The hosted runner: GitHub Actions 147 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.usbdeviceforensics)
The hosted runner: GitHub Actions 182 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.packages.bless)
The hosted runner: GitHub Actions 207 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.stix-validator)
The hosted runner: GitHub Actions 221 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.packages.cryptcat)
The hosted runner: GitHub Actions 335 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.packages.python3-pypff)
The hosted runner: GitHub Actions 398 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.packages.dotnet)
The hosted runner: GitHub Actions 403 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.packages.libext2fs2)
The hosted runner: GitHub Actions 429 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.packages.libicu)
The hosted runner: GitHub Actions 441 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.python3-packages.machinae)
The hosted runner: GitHub Actions 437 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.packages.libncurses)
The hosted runner: GitHub Actions 449 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
test_states (3007, 24.04, sift.scripts.amcache)
The hosted runner: GitHub Actions 478 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
changed_states
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
changed_states
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
changed_states
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
changed_states
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
changed_states
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
changed_states
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
changed_states
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|