fix: resolve module name mismatch causing Integration Test failures o… #5
jj-devhubcode-quality.yml
on: push
Rust Code Quality
22s
Python Code Quality
13s
YAML and Config Quality
8s
Security Scan
2m 57s
Documentation Quality
14s
Matrix: Integration Test
Annotations
33 errors, 10 warnings, and 5 notices
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L70
70:1 [trailing-spaces] trailing spaces
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L62
62:1 [trailing-spaces] trailing spaces
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L50
50:81 [line-length] line too long (127 > 80 characters)
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L47
47:81 [line-length] line too long (93 > 80 characters)
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L44
44:1 [trailing-spaces] trailing spaces
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L39
39:1 [trailing-spaces] trailing spaces
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L33
33:5 [indentation] wrong indentation: expected 6 but found 4
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L31
31:1 [trailing-spaces] trailing spaces
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L5
5:21 [brackets] too many spaces inside brackets
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L5
5:16 [brackets] too many spaces inside brackets
|
|
Python Code Quality
Process completed with exit code 1.
|
|
Integration Test (windows-latest, 3.13)
Process completed with exit code 1.
|
|
Integration Test (macos-latest, 3.9)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (windows-latest, 3.11)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (ubuntu-latest, 3.8)
The operation was canceled.
|
|
Integration Test (ubuntu-latest, 3.8)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (ubuntu-latest, 3.10)
The operation was canceled.
|
|
Integration Test (ubuntu-latest, 3.10)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (ubuntu-latest, 3.13)
The operation was canceled.
|
|
Integration Test (ubuntu-latest, 3.13)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (windows-latest, 3.10)
Process completed with exit code 1.
|
|
Integration Test (windows-latest, 3.10)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (windows-latest, 3.8)
The operation was canceled.
|
|
Integration Test (windows-latest, 3.8)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (macos-latest, 3.8)
The operation was canceled.
|
|
Integration Test (macos-latest, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1
[notice] To update, run: python3.8 -m pip install --upgrade pip
|
|
Integration Test (macos-latest, 3.8)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (windows-latest, 3.9)
The operation was canceled.
|
|
Integration Test (windows-latest, 3.9)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Integration Test (windows-latest, 3.12)
The operation was canceled.
|
|
Integration Test (windows-latest, 3.12)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
Security Scan
Process completed with exit code 1.
|
|
Integration Test (macos-latest, 3.13)
The strategy configuration was canceled because "integration-test.windows-latest_3_13" failed
|
|
YAML and Config Quality:
.github/workflows/publish.yml#L3
3:1 [truthy] truthy value should be one of [false, true]
|
|
YAML and Config Quality:
.github/workflows/publish.yml#L1
1:1 [document-start] missing document start "---"
|
|
YAML and Config Quality:
.github/workflows/ci.yml#L3
3:1 [truthy] truthy value should be one of [false, true]
|
|
YAML and Config Quality:
.github/workflows/ci.yml#L1
1:1 [document-start] missing document start "---"
|
|
YAML and Config Quality:
.github/workflows/code-quality.yml#L3
3:1 [truthy] truthy value should be one of [false, true]
|
|
YAML and Config Quality:
.github/workflows/code-quality.yml#L1
1:1 [document-start] missing document start "---"
|
|
YAML and Config Quality:
.github/workflows/version-bump.yml#L3
3:1 [truthy] truthy value should be one of [false, true]
|
|
YAML and Config Quality:
.github/workflows/version-bump.yml#L1
1:1 [document-start] missing document start "---"
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L3
3:1 [truthy] truthy value should be one of [false, true]
|
|
YAML and Config Quality:
.github/workflows/auto-release.yml#L1
1:1 [document-start] missing document start "---"
|
|
Integration Test (windows-latest, 3.13)
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
|
|
Integration 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
|
|
Integration Test (windows-latest, 3.8)
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
|
|
Integration Test (windows-latest, 3.9)
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
|
|
Integration 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
|