Skip to content
Linter

UnixPB: Ensure CC environment variable is always set for NASM compilation #2786

Sign in to view logs

UnixPB: Ensure CC environment variable is always set for NASM compilation

UnixPB: Ensure CC environment variable is always set for NASM compilation #2786

Triggered via pull request December 5, 2023 13:58
@steelhead31steelhead31
opened #3283
steelhead31:fix_nasm
Status Failure
Total duration 1m 43s
Artifacts –

linter.yml

on: pull_request
Yamllint
17s
Yamllint
Ansible Lint
1m 32s
Ansible Lint
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Yamllint: ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/nasm/tasks/main.yml#L91
91:11 [indentation] wrong indentation: expected 4 but found 10
yaml[indentation]: ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/nasm/tasks/main.yml#L91
Wrong indentation: expected 4 but found 10
Ansible Lint
Process completed with exit code 2.
Yamllint
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/
Ansible Lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@75f3110429a8c05be0e1bf360334e4cced2b63fa. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/