fix: add spec version header to polling connector requests #1674
Triggered via pull request
September 5, 2025 13:11
Tymek
Status
Success
Total duration
15m 13s
Artifacts
–
Annotations
20 errors and 6 notices
|
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
|
|
tox (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
|
|
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (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
|
|
tox (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
|
|
tox (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
|
|
tox (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
|
|
tox (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
|
|
tox (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
|