Skip to content

Ruff

Ruff #7510

Triggered via pull request November 24, 2024 21:52
@doomedravendoomedraven
synchronize #2410
ruff
Status Failure
Total duration 1m 7s
Artifacts

python-package.yml

on: pull_request
Matrix: format
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Ruff (G004): analyzer/linux/analyzer.py#L74
analyzer/linux/analyzer.py:74:22: G004 Logging statement uses f-string
Ruff (G004): analyzer/linux/analyzer.py#L121
analyzer/linux/analyzer.py:121:31: G004 Logging statement uses f-string
Ruff (G004): analyzer/linux/analyzer.py#L126
analyzer/linux/analyzer.py:126:19: G004 Logging statement uses f-string
Ruff (G004): analyzer/linux/analyzer.py#L128
analyzer/linux/analyzer.py:128:19: G004 Logging statement uses f-string
Ruff (G004): analyzer/linux/analyzer.py#L134
analyzer/linux/analyzer.py:134:19: G004 Logging statement uses f-string
Ruff (G004): analyzer/linux/lib/api/screenshot.py#L142
analyzer/linux/lib/api/screenshot.py:142:30: G004 Logging statement uses f-string
Ruff (G004): analyzer/linux/lib/api/screenshot.py#L263
analyzer/linux/lib/api/screenshot.py:263:33: G004 Logging statement uses f-string
Ruff (G201): analyzer/linux/lib/common/results.py#L41
analyzer/linux/lib/common/results.py:41:13: G201 Logging `.exception(...)` should be used instead of `.error(..., exc_info=True)`
Ruff (G201): analyzer/windows/analyzer.py#L694
analyzer/windows/analyzer.py:694:45: G201 Logging `.exception(...)` should be used instead of `.error(..., exc_info=True)`
Ruff (G201): analyzer/windows/analyzer.py#L918
analyzer/windows/analyzer.py:918:17: G201 Logging `.exception(...)` should be used instead of `.error(..., exc_info=True)`