Skip to content

found a case where jedi's full name did not start with the module nam… #433

found a case where jedi's full name did not start with the module nam…

found a case where jedi's full name did not start with the module nam… #433

Triggered via pull request April 4, 2025 21:15
@alvin-ralvin-r
synchronize #124
jedi_ctx_fix
Status Success
Total duration 5m 31s
Artifacts

unit-tests.yaml

on: pull_request
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
unit-tests (3.10.13)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
unit-tests (3.9.18)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
unit-tests (3.11.6)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
unit-tests (3.12.1)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
unit-tests (3.13.0)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.