Focal loss optimisation #1070
Triggered via pull request
September 14, 2025 14:12
vedantdalimkar
Status
Failure
Total duration
2m 56s
Artifacts
–
tests.yml
on: pull_request
style
8s
test_logits_match
1m 30s
test_torch_compile
2m 16s
test_torch_export
2m 52s
test_torch_script
1m 29s
minimum
2m 15s
Matrix: test
Annotations
21 errors, 15 warnings, and 3 notices
|
style
Process completed with exit code 1.
|
|
Ruff (F841):
segmentation_models_pytorch/losses/focal_loss_optimisation_benchmarking.ipynb#L62
segmentation_models_pytorch/losses/focal_loss_optimisation_benchmarking.ipynb:1:1: F841 Local variable `loss` is assigned to but never used
|
|
test (macos-latest, 3.11)
Process completed with exit code 1.
|
|
test (windows-latest, 3.12)
The operation was canceled.
|
|
test (windows-latest, 3.12)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
test (windows-latest, 3.11)
The operation was canceled.
|
|
test (windows-latest, 3.11)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
test (windows-latest, 3.10)
The operation was canceled.
|
|
test (windows-latest, 3.10)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
test (ubuntu-latest, 3.11)
The operation was canceled.
|
|
test (ubuntu-latest, 3.11)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
test (ubuntu-latest, 3.10)
The operation was canceled.
|
|
test (ubuntu-latest, 3.10)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
test_logits_match
Process completed with exit code 1.
|
|
test (ubuntu-latest, 3.12)
The operation was canceled.
|
|
test (ubuntu-latest, 3.12)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
test (macos-latest, 3.10)
The operation was canceled.
|
|
test (macos-latest, 3.10)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
test (macos-latest, 3.12)
The operation was canceled.
|
|
test (macos-latest, 3.12)
The strategy configuration was canceled because "test.macos-latest_3_11" failed
|
|
minimum
Process completed with exit code 1.
|
|
style
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.
|
|
test (macos-latest, 3.11)
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.
|
|
test (windows-latest, 3.12)
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.
|
|
test (windows-latest, 3.11)
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.
|
|
test (windows-latest, 3.10)
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.
|
|
test (ubuntu-latest, 3.11)
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.
|
|
test (ubuntu-latest, 3.10)
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.
|
|
test_torch_script
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.
|
|
test_logits_match
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.
|
|
test (ubuntu-latest, 3.12)
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.
|
|
test (macos-latest, 3.10)
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.
|
|
test (macos-latest, 3.12)
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.
|
|
minimum
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.
|
|
test_torch_compile
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.
|
|
test_torch_export
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.
|
|
test (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
test (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
test (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|