Skip to content

Resolve used-before-assignment false negative when a function is defined under TYPE_CHECKING #4343

Resolve used-before-assignment false negative when a function is defined under TYPE_CHECKING

Resolve used-before-assignment false negative when a function is defined under TYPE_CHECKING #4343

Triggered via pull request October 19, 2024 07:20
Status Cancelled
Total duration 1m 8s
Artifacts

primer_run_pr.yaml

on: pull_request
Matrix: run-primer
Fit to window
Zoom out
Zoom in

Annotations

16 errors
Run / 3.9 / batch index 2
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.9 / batch index 2
The operation was canceled.
Run / 3.13 / batch index 3
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.13 / batch index 3
The operation was canceled.
Run / 3.13 / batch index 2
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.13 / batch index 2
The operation was canceled.
Run / 3.9 / batch index 0
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.9 / batch index 0
The operation was canceled.
Run / 3.13 / batch index 0
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.13 / batch index 0
The operation was canceled.
Run / 3.13 / batch index 1
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.13 / batch index 1
The operation was canceled.
Run / 3.9 / batch index 1
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.9 / batch index 1
The operation was canceled.
Run / 3.9 / batch index 3
Canceling since a higher priority waiting request for 'Primer / Run-10034' exists
Run / 3.9 / batch index 3
The operation was canceled.