BUG FIX: issue:493 Loss of task_id when using retry middlewares #883
Triggered via pull request
September 25, 2025 18:45
GefMar
Status
Failure
Total duration
1m 19s
Artifacts
–
Annotations
47 errors and 5 notices
|
pytest (3.10, <2, ubuntu-latest)
Process completed with exit code 1.
|
|
pytest (3.12, <2, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.12, >=2.5,<3, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.11, >=2.5,<3, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.11, <2, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.9, <2, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.11, <2, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.12, <2, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.12, >=2.5,<3, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.12, >=2.5,<3, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.10, <2, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.13, >=2.5,<3, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.13, <2, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.11, <2, ubuntu-latest)
Process completed with exit code 1.
|
|
pytest (3.11, <2, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.11, >=2.5,<3, ubuntu-latest)
The operation was canceled.
|
|
pytest (3.11, >=2.5,<3, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.12, <2, ubuntu-latest)
The operation was canceled.
|
|
pytest (3.12, <2, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.9, <2, ubuntu-latest)
The operation was canceled.
|
|
pytest (3.9, <2, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.9, >=2.5,<3, macos-latest)
The operation was canceled.
|
|
pytest (3.9, >=2.5,<3, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.9, >=2.5,<3, ubuntu-latest)
The operation was canceled.
|
|
pytest (3.9, >=2.5,<3, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.10, >=2.5,<3, macos-latest)
The operation was canceled.
|
|
pytest (3.10, >=2.5,<3, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.13, <2, ubuntu-latest)
The operation was canceled.
|
|
pytest (3.13, <2, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.10, <2, macos-latest)
The operation was canceled.
|
|
pytest (3.10, <2, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.13, >=2.5,<3, ubuntu-latest)
The operation was canceled.
|
|
pytest (3.13, >=2.5,<3, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.13, <2, windows-latest)
The operation was canceled.
|
|
pytest (3.13, <2, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.11, >=2.5,<3, windows-latest)
The operation was canceled.
|
|
pytest (3.11, >=2.5,<3, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.10, >=2.5,<3, ubuntu-latest)
The operation was canceled.
|
|
pytest (3.10, >=2.5,<3, ubuntu-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.13, >=2.5,<3, macos-latest)
The operation was canceled.
|
|
pytest (3.13, >=2.5,<3, macos-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.10, >=2.5,<3, windows-latest)
The operation was canceled.
|
|
pytest (3.10, >=2.5,<3, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.9, >=2.5,<3, windows-latest)
The operation was canceled.
|
|
pytest (3.9, <2, windows-latest)
The operation was canceled.
|
|
pytest (3.9, <2, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.9, >=2.5,<3, windows-latest)
The strategy configuration was canceled because "pytest._3_10__2_ubuntu-latest" failed
|
|
pytest (3.13, <2, windows-latest)
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
|
|
pytest (3.11, >=2.5,<3, windows-latest)
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
|
|
pytest (3.10, >=2.5,<3, windows-latest)
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
|
|
pytest (3.9, <2, windows-latest)
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
|
|
pytest (3.9, >=2.5,<3, windows-latest)
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
|