Skip to content

fix: get rid of url.parse in network code #2

fix: get rid of url.parse in network code

fix: get rid of url.parse in network code #2

Triggered via push June 24, 2025 13:40
Status Failure
Total duration 11h 33m 51s
Artifacts
build-playwright-driver
1m 23s
build-playwright-driver
Matrix: chromium_tot
Matrix: chromium_tot_headless_shell
Matrix: firefox_beta
Matrix: headed_tests
Matrix: test-package-installations-other-node-versions
Matrix: Test channel=chromium
Matrix: test_chromium_channels
Matrix: test_linux
Matrix: test_mac
Matrix: Windows
Matrix: tracing_linux
Matrix: Transport
Fit to window
Zoom out
Zoom in

Annotations

24 errors
macos-15-xlarge (webkit)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-13-large (firefox)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-15-large (webkit)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-13-large (chromium)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-14-large (firefox)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-13-xlarge (chromium)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-13-xlarge (webkit)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-13-xlarge (firefox)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-14-large (webkit)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-14-large (chromium)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-14-xlarge (webkit)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-14-xlarge (chromium)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-14-xlarge (firefox)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
headed chromium (macos-14-xlarge)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
headed firefox (macos-14-xlarge)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
macos-13-large (webkit)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
headed webkit (macos-14-xlarge)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings
Test channel=chromium (macos-latest)
Process completed with exit code 1.
Tracing webkit
Process completed with exit code 1.
Test chrome on macos-latest
Process completed with exit code 1.
Test msedge on 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.
Test msedge-dev on 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.
Test chrome-beta on macos-latest
Process completed with exit code 1.
Test msedge on macos-latest
Process completed with exit code 1.