Skip to content

False positive "non-empty-array<int, int> might not be a list" when c… #22859

False positive "non-empty-array<int, int> might not be a list" when c…

False positive "non-empty-array<int, int> might not be a list" when c… #22859

Triggered via push September 25, 2025 07:51
Status Failure
Total duration 49m 40s
Artifacts

tests.yml

on: push
Determine levels tests matrix
40s
Determine levels tests matrix
Matrix: Integration tests
Matrix: Tests with old PHPUnit
Matrix: Tests
Matrix: Levels tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 6 warnings, and 8 notices
Integration tests (windows-latest)
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (codeload.github.com:443)
Tests (8.4, windows-latest)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Integration tests (windows-latest)
Back off 22.47 seconds before retry.
Integration tests (windows-latest)
Failed to download action 'https://api.github.com/repos/shivammathur/setup-php/zipball/bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.github.com:443)
Integration tests (windows-latest)
Back off 27.969 seconds before retry.
Integration tests (windows-latest)
Failed to download action 'https://api.github.com/repos/shivammathur/setup-php/zipball/bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.github.com:443)
Tests (8.2, windows-latest)
Back off 23.334 seconds before retry.
Tests (8.2, windows-latest)
Failed to download action 'https://api.github.com/repos/ramsey/composer-install/zipball/3cf229dc2919194e9e36783941438d17239e8520'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.github.com:443)
Integration tests (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
Tests (8.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
Tests with old PHPUnit (8.0, 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
Tests with old PHPUnit (8.1, 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
Tests (8.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
Tests (8.5, 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
Tests with old PHPUnit (7.4, 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
Tests (8.4, 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