Skip to content

[FIX] Do not require notch frequencies to be parsed as numbers, accommodating multiples #1194

[FIX] Do not require notch frequencies to be parsed as numbers, accommodating multiples

[FIX] Do not require notch frequencies to be parsed as numbers, accommodating multiples #1194

Triggered via pull request September 8, 2023 12:36
Status Cancelled
Total duration 29s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

validation.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 errors
yamllint
Canceling since a higher priority waiting request for 'Validation-refs/pull/1605/merge' exists
yamllint
The operation was canceled.
python-style
Canceling since a higher priority waiting request for 'Validation-refs/pull/1605/merge' exists
python-style
The operation was canceled.
codespell
Canceling since a higher priority waiting request for 'Validation-refs/pull/1605/merge' exists
codespell
The operation was canceled.
validate_cff
Canceling since a higher priority waiting request for 'Validation-refs/pull/1605/merge' exists
validate_cff
The operation was canceled.
remark
Canceling since a higher priority waiting request for 'Validation-refs/pull/1605/merge' exists
remark
The operation was canceled.
latin-phrases
Canceling since a higher priority waiting request for 'Validation-refs/pull/1605/merge' exists
latin-phrases
The operation was canceled.