Skip to content

chore: refactor e2e tests to playwright #6537

chore: refactor e2e tests to playwright

chore: refactor e2e tests to playwright #6537

Triggered via pull request July 31, 2024 02:59
Status Failure
Total duration 9m 4s
Artifacts

nodejs.yml

on: pull_request
Matrix: lint
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

268 errors, 20 warnings, and 13 notices
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v22.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (2/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (3/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v20.x, Webpack latest (4/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-of-the-host-option-from-the-client-webSocketURL-option-if-options-allowedHosts-is-auto-response-status-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-connect-web-socket-client-using-custom-hostname-to-web-socket-server-with-the-custom-hostname-value-starting-with-dot-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-sockjs-page-errors-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-console-messages-snap.webpack5: Filename too long
Test - windows-latest - Node v18.x, Webpack latest (1/4)
unable to create file test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-should-disconnect-web-socket-client-using-custom-hostname-from-web-socket-server-with-the-auto-value-based-on-the-host-header-when-server-https-is-enabled-ws-page-errors-snap.webpack5: Filename too long
Lint - ubuntu-latest - Node vlts/*
Process completed with exit code 1.
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-console-messges-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/Users/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:202:10
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/Users/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:203:28
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-console-messges-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:202:10
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:203:28
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-console-messges-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:202:10
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:203:28
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws"): test/e2e/web-socket-communication.test.js#L110
1) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs"): test/e2e/web-socket-communication.test.js#L110
2) [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: 0 Received: 1 108 | 109 | // this fails > 110 | expect(server.webSocketServer.clients.length).toBe(0); | ^ 111 | expect( 112 | consoleMessages.map((message) => message.text()), 113 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-communication.test.js:110:57
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-console-messges-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:202:10
[chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy: test/helpers/playwright-custom-expects.js#L41
3) [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/web-socket-server-url.test.js/web-socket-server-URL-should-work-behind-proxy-when-hostnames-are-different-and-ports-are-same-ws-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/web-socket-server-url.test.js:203:28
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Error: Screenshot comparison failed: 138 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 138 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 138 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 138 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 138 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 138 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 138 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 138 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 138 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 138 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 138 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 138 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Error: Screenshot comparison failed: 214 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 214 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 214 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 214 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 214 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 214 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 214 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 214 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 214 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 214 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 214 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 214 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium-retry1/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/): test/e2e/server.test.js#L83
1) [chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/) Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium/server-option-as-string-ht-299e6-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium/server-option-as-string-ht-299e6-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toBe(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect(consoleMessages.map((message) => message.text())).toMatchSnapshotWithArray("console messages"); 86 | at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:83:28
[chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/): test/e2e/server.test.js#L83
1) [chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium-retry1/server-option-as-string-ht-299e6-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium-retry1/server-option-as-string-ht-299e6-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toBe(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect(consoleMessages.map((message) => message.text())).toMatchSnapshotWithArray("console messages"); 86 | at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:83:28
[chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/): test/e2e/server.test.js#L83
1) [chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium-retry2/server-option-as-string-ht-299e6-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium-retry2/server-option-as-string-ht-299e6-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toBe(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect(consoleMessages.map((message) => message.text())).toMatchSnapshotWithArray("console messages"); 86 | at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:83:28
[chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/): test/e2e/server.test.js#L83
1) [chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium-retry3/server-option-as-string-ht-299e6-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-5962b-GET-request-to-index-route--chromium-retry3/server-option-as-string-ht-299e6-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toBe(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect(consoleMessages.map((message) => message.text())).toMatchSnapshotWithArray("console messages"); 86 | at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:83:28
[chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/): test/e2e/server.test.js#L138
2) [chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/) Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-custom-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium/server-option-as-string-cu-7ce33-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium/server-option-as-string-cu-7ce33-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 136 | expect(response.status()).toBe(200); 137 | > 138 | await expect(page).toHaveScreenshot(); | ^ 139 | 140 | expect( 141 | consoleMessages.map((message) => message.text()) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:138:28
[chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/): test/e2e/server.test.js#L138
2) [chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-custom-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium-retry1/server-option-as-string-cu-7ce33-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium-retry1/server-option-as-string-cu-7ce33-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 136 | expect(response.status()).toBe(200); 137 | > 138 | await expect(page).toHaveScreenshot(); | ^ 139 | 140 | expect( 141 | consoleMessages.map((message) => message.text()) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:138:28
[chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/): test/e2e/server.test.js#L138
2) [chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-custom-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium-retry2/server-option-as-string-cu-7ce33-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium-retry2/server-option-as-string-cu-7ce33-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 136 | expect(response.status()).toBe(200); 137 | > 138 | await expect(page).toHaveScreenshot(); | ^ 139 | 140 | expect( 141 | consoleMessages.map((message) => message.text()) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:138:28
[chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/): test/e2e/server.test.js#L138
2) [chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-custom-http-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium-retry3/server-option-as-string-cu-7ce33-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-f28a2-GET-request-to-index-route--chromium-retry3/server-option-as-string-cu-7ce33-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 136 | expect(response.status()).toBe(200); 137 | > 138 | await expect(page).toHaveScreenshot(); | ^ 139 | 140 | expect( 141 | consoleMessages.map((message) => message.text()) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:138:28
[chromium] › server.test.js:174:7 › server option › as string › https › should handle GET request to index route (/): test/e2e/server.test.js#L195
3) [chromium] › server.test.js:174:7 › server option › as string › https › should handle GET request to index route (/) Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-https-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-fa7de-GET-request-to-index-route--chromium/server-option-as-string-ht-6d576-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-fa7de-GET-request-to-index-route--chromium/server-option-as-string-ht-6d576-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 193 | expect(response.status()).toBe(200); 194 | > 195 | await expect(page).toHaveScreenshot(); | ^ 196 | 197 | expect(consoleMessages.map((message) => message.text())).toMatchSnapshotWithArray("console messages"); 198 | at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:195:28
[chromium] › server.test.js:174:7 › server option › as string › https › should handle GET request to index route (/): test/e2e/server.test.js#L195
3) [chromium] › server.test.js:174:7 › server option › as string › https › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 69 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/server.test.js/server-option-as-string-https-should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-fa7de-GET-request-to-index-route--chromium-retry1/server-option-as-string-ht-6d576-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/server-server-option-as-st-fa7de-GET-request-to-index-route--chromium-retry1/server-option-as-string-ht-6d576-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 69 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 69 pixels (ratio 0.01 of all image pixels) are different. 193 | expect(response.status()).toBe(200); 194 | > 195 | await expect(page).toHaveScreenshot(); | ^ 196 | 197 | expect(consoleMessages.map((message) => message.text())).toMatchSnapshotWithArray("console messages"); 198 | at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/server.test.js:195:28
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/home/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/home/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium-retry1/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/home/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/home/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium-retry1/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-response-status-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1347:37
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-console-messages-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1350:13
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1351:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/helpers/playwright-test.js#L3
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Error: Requiring @playwright/test second time, First: Error: at ../helpers/playwright-test.js:3 1 | "use strict"; 2 | > 3 | const { test, mergeTests } = require("@playwright/test"); | ^ 4 | 5 | const customTest = test.extend({ 6 | // eslint-disable-next-line no-empty-pattern at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/index.js:69:33) at Module._compile (node:internal/modules/cjs/loader:1504:14) at Module._extensions..js (node:internal/modules/cjs/loader:1588:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1282:32) at Function.Module._load (node:internal/modules/cjs/loader:1098:12) at TracingChannel.traceSync (node:diagnostics_channel:315:14) at wrapModuleLoad (node:internal/modules/cjs/loader:215:24) at Module.require (node:internal/modules/cjs/loader:1304:12) at require (node:internal/modules/helpers:123:16) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/test.js:17:13) at Module._compile (node:internal/modules/cjs/loader:1504:14) at Module._extensions..js (node:internal/modules/cjs/loader:1588:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1282:32) at Function.Module._load (node:internal/modules/cjs/loader:1098:12) at TracingChannel.traceSync (node:diagnostics_channel:315:14) at wrapModuleLoad (node:internal/modules/cjs/loader:215:24) at Module.require (node:internal/modules/cjs/loader:1304:12) at require (node:internal/modules/helpers:123:16) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/@playwright/test/index.js:17:18) at Module._compile (node:internal/modules/cjs/loader:1504:14) at Module._extensions..js (node:internal/modules/cjs/loader:1588:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1282:32) at Function.Module._load (node:internal/modules/cjs/loader:1098:12) at TracingChannel.traceSync (node:diagnostics_channel:315:14) at wrapModuleLoad (node:internal/modules/cjs/loader:215:24) at Module.require (node:internal/modules/cjs/loader:1304:12) at require (node:internal/modules/helpers:123:16) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-test.js:3:30) at Module._compile (node:internal/modules/cjs/loader:1504:14) at Module.f._compile (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:994) at Module._extensions..js (node:internal/modules/cjs/loader:1588:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1282:32) at Function.Module._load (node:internal/modules/cjs/loader:1098:12) at TracingChannel.traceSync (node:diagnostics_channel:315:14) at wrapModuleLoad (node:internal/modules/cjs/loader:215:24) at Module.require (node:internal/modules/cjs/loader:1304:12) at require (node:internal/mod
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry1/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry2/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route: test/e2e/on-listening.test.js#L83
1) [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 120 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-GET-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-412f5-o-listening-some-path-route-chromium-retry3/onListening-option-should--0d619-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 120 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 120 pixels (ratio 0.01 of all image pixels) are different. 81 | expect(response.status()).toEqual(200); 82 | > 83 | await expect(page).toHaveScreenshot(); | ^ 84 | 85 | expect( 86 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:83:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry1/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry2/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route: test/e2e/on-listening.test.js#L122
2) [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 183 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/on-listening.test.js/onListening-option-should-handle-POST-request-to-listening-some-path-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/on-listening-onListening-o-998a3-o-listening-some-path-route-chromium-retry3/onListening-option-should--e3b4d-listening-some-path-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 183 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 183 pixels (ratio 0.01 of all image pixels) are different. 120 | expect(response.status()).toEqual(200); 121 | > 122 | await expect(page).toHaveScreenshot(); | ^ 123 | 124 | expect( 125 | consoleMessages.map((message) => message.text()), at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/on-listening.test.js:122:24
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/home/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation: test/e2e/overlay.test.js#L115
3) [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ─── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toMatchSnapshotWithArray(expected) Expected: "/home/runner/work/webpack-dev-server/webpack-dev-server/test-results/overlay-overlay-should-sho-67c2b-ing-for-initial-compilation-chromium-retry1/overlay-should-show-a-warning-for-initial-compilation-page-html-snap-actual.webpack5" Received: "<body> <h1>webpack-dev-server is running...</h1> <script type=\"text/javascript\" charset=\"utf-8\" src=\"/main.js\"></script>· <iframe id=\"webpack-dev-server-client-overlay\" src=\"about:blank\" style=\" position: fixed; inset: 0px; width: 100vw; height: 100vh; border: none; z-index: 2147483647; \" ></iframe> </body> " 113 | plugins: [prettierHTML, prettierCSS], 114 | }), > 115 | ).toMatchSnapshotWithArray("page html"); | ^ 116 | expect( 117 | await prettier.format(overlayHtml, { 118 | parser: "html", at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/overlay.test.js:115:9
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-response-status-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1347:37
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-console-messages-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1350:13
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1351:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/helpers/playwright-test.js#L3
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Error: Requiring @playwright/test second time, First: Error: at ../helpers/playwright-test.js:3 1 | "use strict"; 2 | > 3 | const { test, mergeTests } = require("@playwright/test"); | ^ 4 | 5 | const customTest = test.extend({ 6 | // eslint-disable-next-line no-empty-pattern at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/index.js:69:33) at Module._compile (node:internal/modules/cjs/loader:1358:14) at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1208:32) at Function.Module._load (node:internal/modules/cjs/loader:1024:12) at Module.require (node:internal/modules/cjs/loader:1233:19) at require (node:internal/modules/helpers:179:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/test.js:17:13) at Module._compile (node:internal/modules/cjs/loader:1358:14) at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1208:32) at Function.Module._load (node:internal/modules/cjs/loader:1024:12) at Module.require (node:internal/modules/cjs/loader:1233:19) at require (node:internal/modules/helpers:179:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/@playwright/test/index.js:17:18) at Module._compile (node:internal/modules/cjs/loader:1358:14) at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1208:32) at Function.Module._load (node:internal/modules/cjs/loader:1024:12) at Module.require (node:internal/modules/cjs/loader:1233:19) at require (node:internal/modules/helpers:179:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-test.js:3:30) at Module._compile (node:internal/modules/cjs/loader:1358:14) at Module.f._compile (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:994) at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1208:32) at Function.Module._load (node:internal/modules/cjs/loader:1024:12) at Module.require (node:internal/modules/cjs/loader:1233:19) at require (node:internal/modules/helpers:179:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/api.test.js:6:18) at Module._compile (node:internal/modules/cjs/loader:1358:14) at Module.f._compile (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:994) at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_m
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-response-status-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/Users/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1347:37
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-console-messages-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/Users/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1350:13
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/Users/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1351:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/helpers/playwright-test.js#L3
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Error: Requiring @playwright/test second time, First: Error: at ../helpers/playwright-test.js:3 1 | "use strict"; 2 | > 3 | const { test, mergeTests } = require("@playwright/test"); | ^ 4 | 5 | const customTest = test.extend({ 6 | // eslint-disable-next-line no-empty-pattern at Object.<anonymous> (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/index.js:69:33) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/test.js:17:13) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/@playwright/test/index.js:17:18) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/Users/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-test.js:3:30) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module.f._compile (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:994) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/api.test.js:6:18) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module.f._compile (/Users/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:994) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/Users/runner/work/webpack-dev-server/webpack-dev-s
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 465 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 465 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 465 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 465 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 465 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 465 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 465 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 465 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 465 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 465 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 465 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 465 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 465 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 465 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 465 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 465 pixels (ratio 0.01 of all image pixels) are different. Expected: /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /Users/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 465 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 465 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /Users/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-response-status-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1347:37
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-console-messages-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1350:13
[chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto: test/helpers/playwright-custom-expects.js#L41
1) [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto Error: A snapshot doesn't exist at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/allowed-hosts.test.js/allowed-hosts-check-host-headers-should-always-allow-value-from-the-host-options-if-options-allowedHosts-is-auto-page-errors-snap.webpack5, writing actual. at ../helpers/playwright-custom-expects.js:41 39 | try { 40 | const serialized = JSON.stringify(received); > 41 | await expect(serialized).toMatchSnapshot({ | ^ 42 | name: snapshotFilePath, 43 | }); 44 | pass = true; at Object.toMatchSnapshotWithArray (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-custom-expects.js:41:32) at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/allowed-hosts.test.js:1351:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/helpers/playwright-test.js#L3
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Error: Requiring @playwright/test second time, First: Error: at ../helpers/playwright-test.js:3 1 | "use strict"; 2 | > 3 | const { test, mergeTests } = require("@playwright/test"); | ^ 4 | 5 | const customTest = test.extend({ 6 | // eslint-disable-next-line no-empty-pattern at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/index.js:69:33) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/test.js:17:13) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/@playwright/test/index.js:17:18) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/test/helpers/playwright-test.js:3:30) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module.f._compile (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:994) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:1010) at Module.load (node:internal/modules/cjs/loader:1203:32) at Function.Module._load (node:internal/modules/cjs/loader:1019:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/api.test.js:6:18) at Module._compile (node:internal/modules/cjs/loader:1364:14) at Module.f._compile (/home/runner/work/webpack-dev-server/webpack-dev-server/node_modules/playwright/lib/utilsBundleImpl.js:16:994) at Module._extensions..js (node:internal/modules/cjs/loader:1422:10) at Object.i.<computed>.ut._extensions.<computed> [as .js] (/home/runner/work/webpack-dev-server/webpack-dev-server/node_m
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
2) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-6efea--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-f48d6-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-6efea-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry1/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry2/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
[chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/): test/e2e/app.test.js#L97
3) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 494 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/__snapshots__/app.test.js/app-option-should-work-using-express-applica-a1fb3--should-handle-GET-request-to-index-route-1.png Received: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-actual.png Diff: /home/runner/work/webpack-dev-server/webpack-dev-server/test-results/app-app-option-should-work-15bf8-GET-request-to-index-route--chromium-retry3/app-option-should-work-usi-a1fb3-equest-to-index-route-1-diff.png Call log: - expect.toHaveScreenshot with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 494 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 494 pixels (ratio 0.01 of all image pixels) are different. 95 | 96 | expect(response.status()).toEqual(200); > 97 | await expect(page).toHaveScreenshot(); | ^ 98 | expect( 99 | consoleMessages.map((message) => message.text()), 100 | ).toMatchSnapshotWithArray("console messages"); at /home/runner/work/webpack-dev-server/webpack-dev-server/test/e2e/app.test.js:97:30
Test - macos-latest - Node v22.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v22.x-latest-2/4-refs/pull/5080/merge' exists
Test - macos-latest - Node v22.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v22.x-latest-3/4-refs/pull/5080/merge' exists
Test - macos-latest - Node v22.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v22.x-latest-1/4-refs/pull/5080/merge' exists
Test - macos-latest - Node v20.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v20.x-latest-4/4-refs/pull/5080/merge' exists
Test - macos-latest - Node v22.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v22.x-latest-4/4-refs/pull/5080/merge' exists
Test - ubuntu-latest - Node v18.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for 'test-ubuntu-latest-v18.x-latest-3/4-refs/pull/5080/merge' exists
Test - ubuntu-latest - Node v18.x, Webpack latest (3/4)
The operation was canceled.
Test - ubuntu-latest - Node v20.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for 'test-ubuntu-latest-v20.x-latest-3/4-refs/pull/5080/merge' exists
Test - ubuntu-latest - Node v20.x, Webpack latest (3/4)
The operation was canceled.
Test - macos-latest - Node v20.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v20.x-latest-2/4-refs/pull/5080/merge' exists
Test - macos-latest - Node v20.x, Webpack latest (2/4)
The operation was canceled.
Test - ubuntu-latest - Node v22.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for 'test-ubuntu-latest-v22.x-latest-3/4-refs/pull/5080/merge' exists
Test - ubuntu-latest - Node v22.x, Webpack latest (3/4)
The operation was canceled.
Test - macos-latest - Node v20.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v20.x-latest-3/4-refs/pull/5080/merge' exists
Test - macos-latest - Node v20.x, Webpack latest (3/4)
The operation was canceled.
Test - macos-latest - Node v20.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for 'test-macos-latest-v20.x-latest-1/4-refs/pull/5080/merge' exists
Test - macos-latest - Node v20.x, Webpack latest (1/4)
The operation was canceled.
Slow Test: [chromium] › watch-files.test.js#L1
[chromium] › watch-files.test.js took 22.9s
Slow Test: [chromium] › watch-files.test.js#L1
[chromium] › watch-files.test.js took 22.6s
Slow Test: [chromium] › watch-files.test.js#L1
[chromium] › watch-files.test.js took 22.5s
Slow Test: [chromium] › watch-files.test.js#L1
[chromium] › watch-files.test.js took 21.8s
Slow Test: [chromium] › hot-and-live-reload.test.js#L1
[chromium] › hot-and-live-reload.test.js took 27.7s
Slow Test: [chromium] › multi-compiler.test.js#L1
[chromium] › multi-compiler.test.js took 21.4s
Slow Test: [chromium] › logging.test.js#L1
[chromium] › logging.test.js took 19.0s
Slow Test: [chromium] › hot-and-live-reload.test.js#L1
[chromium] › hot-and-live-reload.test.js took 28.4s
Slow Test: [chromium] › multi-compiler.test.js#L1
[chromium] › multi-compiler.test.js took 21.4s
Slow Test: [chromium] › logging.test.js#L1
[chromium] › logging.test.js took 19.0s
Slow Test: [chromium] › hot-and-live-reload.test.js#L1
[chromium] › hot-and-live-reload.test.js took 27.8s
Slow Test: [chromium] › multi-compiler.test.js#L1
[chromium] › multi-compiler.test.js took 21.5s
Slow Test: [chromium] › logging.test.js#L1
[chromium] › logging.test.js took 19.0s
Slow Test: [chromium] › client-reconnect.test.js#L1
[chromium] › client-reconnect.test.js took 34.7s
Slow Test: [chromium] › hot-and-live-reload.test.js#L1
[chromium] › hot-and-live-reload.test.js took 29.0s
Slow Test: [chromium] › multi-compiler.test.js#L1
[chromium] › multi-compiler.test.js took 21.4s
Slow Test: [chromium] › logging.test.js#L1
[chromium] › logging.test.js took 19.2s
Slow Test: [chromium] › client-reconnect.test.js#L1
[chromium] › client-reconnect.test.js took 34.7s
Slow Test: [chromium] › client-reconnect.test.js#L1
[chromium] › client-reconnect.test.js took 35.2s
Slow Test: [chromium] › client-reconnect.test.js#L1
[chromium] › client-reconnect.test.js took 34.9s
🎭 Playwright Run Summary
14 failed [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("ws") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("ws") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("ws") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("ws") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("ws") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("sockjs") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("sockjs") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("sockjs") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("sockjs") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("sockjs") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("sockjs") 103 passed (2.1m)
🎭 Playwright Run Summary
14 failed [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("ws") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("ws") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("ws") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("ws") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("ws") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("sockjs") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("sockjs") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("sockjs") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("sockjs") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("sockjs") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("sockjs") 103 passed (2.2m)
🎭 Playwright Run Summary
14 failed [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("ws") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("ws") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("ws") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("ws") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("ws") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("sockjs") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("sockjs") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("sockjs") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("sockjs") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("sockjs") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("sockjs") 103 passed (2.2m)
🎭 Playwright Run Summary
14 failed [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("ws") [chromium] › web-socket-communication.test.js:69:5 › web socket communication › should work and terminate client that is not alive ("sockjs") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("ws") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("ws") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("ws") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("ws") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("ws") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("ws") [chromium] › web-socket-server-url.test.js:115:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are same ("sockjs") [chromium] › web-socket-server-url.test.js:212:5 › web socket server URL › should work behind proxy, when hostnames are different and ports are different ("sockjs") [chromium] › web-socket-server-url.test.js:314:5 › web socket server URL › should work behind proxy, when the "host" option is "local-ip" and the "port" option is "auto" ("sockjs") [chromium] › web-socket-server-url.test.js:2034:5 › web socket server URL › should work when "host" option is IPv4 ("sockjs") [chromium] › web-socket-server-url.test.js:2103:5 › web socket server URL › should work when "host" option is "local-ip" ("sockjs") [chromium] › web-socket-server-url.test.js:2173:5 › web socket server URL › should work when "host" option is "local-ipv4" ("sockjs") 103 passed (2.1m)
🎭 Playwright Run Summary
32 failed [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ──── [chromium] › overlay.test.js:129:3 › overlay › should show an error for initial compilation ──── [chromium] › overlay.test.js:175:3 › overlay › should show a warning and error for initial compilation [chromium] › overlay.test.js:227:3 › overlay › should show an ansi formatted error for initial compilation [chromium] › overlay.test.js:277:3 › overlay › should show a warning and error for initial compilation and protects against xss [chromium] › overlay.test.js:326:3 › overlay › should not show initially, then show on an error, then hide on fix [chromium] › overlay.test.js:408:3 › overlay › should not show initially, then show on an error, then show other error, then hide on fix [chromium] › overlay.test.js:518:3 › overlay › should not show initially, then show on an error and allow to close [chromium] › overlay.test.js:699:3 › overlay › should not show a warning when "client.overlay.warnings" is "false" [chromium] › overlay.test.js:743:3 › overlay › should not show warning when it is filtered ───── [chromium] › overlay.test.js:784:3 › overlay › should show warning when it is not filtered ───── [chromium] › overlay.test.js:837:3 › overlay › should show a warning when "client.overlay" is "true" [chromium] › overlay.test.js:888:3 › overlay › should show a warning when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:941:3 › overlay › should show a warning when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1036:3 › overlay › should not show an error when "client.overlay.errors" is "false" [chromium] › overlay.test.js:1080:3 › overlay › should not show error when it is filtered ────── [chromium] › overlay.test.js:1122:3 › overlay › should show error when it is not filtered ────── [chromium] › overlay.test.js:1175:3 › overlay › should show an error when "client.overlay" is "true" [chromium] › overlay.test.js:1226:3 › overlay › should show overlay when Trusted Types are enabled [chromium] › overlay.test.js:1290:3 › overlay › should show overlay when Trusted Types are enabled and the "require-trusted-types-for 'script'" header was used [chromium] › overlay.test.js:1407:3 › overlay › should show an error when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1460:3 › overlay › should show an error when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:1513:3 › overlay › should show a warning and hide them after closing connection [chromium] › overlay.test.js:1586:3 › overlay › should show an error after invalidation ──────── [chromium] › overlay.test.js:1646:3 › overlay › should show a warning after invalidation ─────── [chromium] › overlay.test.js:1706:3 › overlay › should show error for uncaught runtime error ─── [chromium] › overlay.test.js:1751:3 › overlay › should not show filtered runtime error ───────── [chromium] › overlay.test.js:1792:3 › overlay › should show error for uncaught promise rejection [chromium] › overlay.test.js:1839:3 › overlay › should not show filtered promise rejection ───── [chromium] › overlay.test.js:1882:3 › overlay › should show overlay when "Content-Security-Policy" is "default-src 'self'" was used 5 skipped 90 passed (4.9m)
🎭 Playwright Run Summary
40 failed [chromium] › server.test.js:62:7 › server option › as string › http › should handle GET request to index route (/) [chromium] › server.test.js:117:7 › server option › as string › custom-http › should handle GET request to index route (/) [chromium] › server.test.js:174:7 › server option › as string › https › should handle GET request to index route (/) [chromium] › server.test.js:229:7 › server option › as string › spdy › should handle GET request to index route (/) [chromium] › server.test.js:323:7 › server option › as object › ca, pfx, key and cert are array of buffers › should handle GET request to index route (/) [chromium] › server.test.js:403:7 › server option › as object › ca, pfx, key and cert are strings › should handle GET request to index route (/) [chromium] › server.test.js:492:7 › server option › as object › ca, pfx, key and cert are array of strings › should handle GET request to index route (/) [chromium] › server.test.js:558:7 › server option › as object › ca, pfx, key and cert are paths to files › should handle GET request to index route (/) [chromium] › server.test.js:624:7 › server option › as object › ca, pfx, key and cert are array of paths to files › should handle GET request to index route (/) [chromium] › server.test.js:771:7 › server option › as object › ca, pfx, key and cert are buffer › should handle GET request to index route (/) [chromium] › server.test.js:852:7 › server option › as object › ca, pfx, key and cert are buffer, key and pfx are objects › should handle GET request to index route (/) [chromium] › server.test.js:938:7 › server option › as object › ca, pfx, key and cert are strings, key and pfx are objects › should handle GET request to index route (/) [chromium] › server.test.js:1015:7 › server option › as object › allow to pass more options › should handle GET request to index route (/) [chromium] › server.test.js:1147:7 › server option › as object › spdy server with options › should handle GET request to index route (/) [chromium] › server.test.js:1216:7 › server option › as object › custom server with options › should handle GET request to index route (/) [chromium] › setup-middlewares.test.js:81:3 › setupMiddlewares option › should handle GET request to /setup-middleware/some/path route [chromium] › setup-middlewares.test.js:159:3 › setupMiddlewares option › should handle POST request to /setup-middleware/some/path route [chromium] › static-directory.test.js:52:5 › static.directory option › to directory › should handle request to index route [chromium] › static-directory.test.js:76:5 › static.directory option › to directory › should handle request to other file [chromium] › static-directory.test.js:199:5 › static.directory option › test listing files in folders without index.html using the option static.serveIndex: false › should show Heyo. because bar has index.html inside it (200) [chromium] › static-directory.test.js:286:5 › static.directory option › test listing files in folders without index.html using the option static.serveIndex: true › should show Heyo. because bar has index.html inside it (200) [chromium] › static-directory.test.js:372:5 › static.directory option › test listing files in folders without index.html using the default static.serveIndex option (true) › should show Heyo. because bar has index.html inside it (200) [chromium] › static-directory.test.js:426:5 › static.directory option › to multiple directories › should handle request first directory [chromium] › static-directory.test.js:450:5 › static.directory option › to multiple directories › should handle request to second directory [chromium] › static-directory.test.js:598:5 › static.directory option › defaults to PWD › should handle request to /index.html [chromium] › static-public-path.test.js:50:5 › static.publicPath option › to directory › should handle request to index [chromium] › static-public-path.test.js:77:5 › static.publicPath option › to directory › s
🎭 Playwright Run Summary
32 failed [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ──── [chromium] › overlay.test.js:129:3 › overlay › should show an error for initial compilation ──── [chromium] › overlay.test.js:175:3 › overlay › should show a warning and error for initial compilation [chromium] › overlay.test.js:227:3 › overlay › should show an ansi formatted error for initial compilation [chromium] › overlay.test.js:277:3 › overlay › should show a warning and error for initial compilation and protects against xss [chromium] › overlay.test.js:326:3 › overlay › should not show initially, then show on an error, then hide on fix [chromium] › overlay.test.js:408:3 › overlay › should not show initially, then show on an error, then show other error, then hide on fix [chromium] › overlay.test.js:518:3 › overlay › should not show initially, then show on an error and allow to close [chromium] › overlay.test.js:699:3 › overlay › should not show a warning when "client.overlay.warnings" is "false" [chromium] › overlay.test.js:743:3 › overlay › should not show warning when it is filtered ───── [chromium] › overlay.test.js:784:3 › overlay › should show warning when it is not filtered ───── [chromium] › overlay.test.js:837:3 › overlay › should show a warning when "client.overlay" is "true" [chromium] › overlay.test.js:888:3 › overlay › should show a warning when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:941:3 › overlay › should show a warning when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1036:3 › overlay › should not show an error when "client.overlay.errors" is "false" [chromium] › overlay.test.js:1080:3 › overlay › should not show error when it is filtered ────── [chromium] › overlay.test.js:1122:3 › overlay › should show error when it is not filtered ────── [chromium] › overlay.test.js:1175:3 › overlay › should show an error when "client.overlay" is "true" [chromium] › overlay.test.js:1226:3 › overlay › should show overlay when Trusted Types are enabled [chromium] › overlay.test.js:1290:3 › overlay › should show overlay when Trusted Types are enabled and the "require-trusted-types-for 'script'" header was used [chromium] › overlay.test.js:1407:3 › overlay › should show an error when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1460:3 › overlay › should show an error when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:1513:3 › overlay › should show a warning and hide them after closing connection [chromium] › overlay.test.js:1586:3 › overlay › should show an error after invalidation ──────── [chromium] › overlay.test.js:1646:3 › overlay › should show a warning after invalidation ─────── [chromium] › overlay.test.js:1706:3 › overlay › should show error for uncaught runtime error ─── [chromium] › overlay.test.js:1751:3 › overlay › should not show filtered runtime error ───────── [chromium] › overlay.test.js:1792:3 › overlay › should show error for uncaught promise rejection [chromium] › overlay.test.js:1839:3 › overlay › should not show filtered promise rejection ───── [chromium] › overlay.test.js:1882:3 › overlay › should show overlay when "Content-Security-Policy" is "default-src 'self'" was used 5 skipped 90 passed (5.8m)
🎭 Playwright Run Summary
32 failed [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ──── [chromium] › overlay.test.js:129:3 › overlay › should show an error for initial compilation ──── [chromium] › overlay.test.js:175:3 › overlay › should show a warning and error for initial compilation [chromium] › overlay.test.js:227:3 › overlay › should show an ansi formatted error for initial compilation [chromium] › overlay.test.js:277:3 › overlay › should show a warning and error for initial compilation and protects against xss [chromium] › overlay.test.js:326:3 › overlay › should not show initially, then show on an error, then hide on fix [chromium] › overlay.test.js:408:3 › overlay › should not show initially, then show on an error, then show other error, then hide on fix [chromium] › overlay.test.js:518:3 › overlay › should not show initially, then show on an error and allow to close [chromium] › overlay.test.js:699:3 › overlay › should not show a warning when "client.overlay.warnings" is "false" [chromium] › overlay.test.js:743:3 › overlay › should not show warning when it is filtered ───── [chromium] › overlay.test.js:784:3 › overlay › should show warning when it is not filtered ───── [chromium] › overlay.test.js:837:3 › overlay › should show a warning when "client.overlay" is "true" [chromium] › overlay.test.js:888:3 › overlay › should show a warning when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:941:3 › overlay › should show a warning when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1036:3 › overlay › should not show an error when "client.overlay.errors" is "false" [chromium] › overlay.test.js:1080:3 › overlay › should not show error when it is filtered ────── [chromium] › overlay.test.js:1122:3 › overlay › should show error when it is not filtered ────── [chromium] › overlay.test.js:1175:3 › overlay › should show an error when "client.overlay" is "true" [chromium] › overlay.test.js:1226:3 › overlay › should show overlay when Trusted Types are enabled [chromium] › overlay.test.js:1290:3 › overlay › should show overlay when Trusted Types are enabled and the "require-trusted-types-for 'script'" header was used [chromium] › overlay.test.js:1407:3 › overlay › should show an error when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1460:3 › overlay › should show an error when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:1513:3 › overlay › should show a warning and hide them after closing connection [chromium] › overlay.test.js:1586:3 › overlay › should show an error after invalidation ──────── [chromium] › overlay.test.js:1646:3 › overlay › should show a warning after invalidation ─────── [chromium] › overlay.test.js:1706:3 › overlay › should show error for uncaught runtime error ─── [chromium] › overlay.test.js:1751:3 › overlay › should not show filtered runtime error ───────── [chromium] › overlay.test.js:1792:3 › overlay › should show error for uncaught promise rejection [chromium] › overlay.test.js:1839:3 › overlay › should not show filtered promise rejection ───── [chromium] › overlay.test.js:1882:3 › overlay › should show overlay when "Content-Security-Policy" is "default-src 'self'" was used 5 skipped 90 passed (5.8m)
🎭 Playwright Run Summary
29 failed [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "spdy" server › should handle GET request to index route (/) [chromium] › built-in-routes.test.js:123:5 › Built in routes › with simple config › should handle GET request to directory index and list all middleware directories [chromium] › built-in-routes.test.js:271:5 › Built in routes › with multi config › should handle GET request to directory index and list all middleware directories [chromium] › history-api-fallback.test.js:42:5 › historyApiFallback option › as boolean › should handle GET request to directory [chromium] › history-api-fallback.test.js:100:5 › historyApiFallback option › as object › should handle GET request to directory [chromium] › history-api-fallback.test.js:162:5 › historyApiFallback option › as object with static › should handle GET request to directory [chromium] › history-api-fallback.test.js:190:5 › historyApiFallback option › as object with static › should prefer static file over historyApiFallback [chromium] › history-api-fallback.test.js:255:5 › historyApiFallback option › as object with static set to false › historyApiFallback should work and ignore static content [chromium] › history-api-fallback.test.js:328:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites for index [chromium] › history-api-fallback.test.js:356:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites and shows index for unknown urls [chromium] › history-api-fallback.test.js:386:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect any other specified rewrites [chromium] › history-api-fallback.test.js:451:5 › historyApiFallback option › as object with the "verbose" option › request to directory and log [chromium] › history-api-fallback.test.js:522:5 › historyApiFallback option › as object with the "logger" option › request to directory and log [chromium] › history-api-fallback.test.js:590:5 › historyApiFallback option › in-memory files › should take precedence over static files [chromium] › host.test.js:50:5 › host › should work using "local-ip" host and port as number ─── [chromium] › host.test.js:126:5 › host › should work using "local-ip" host and port as string ── [chromium] › host.test.js:198:5 › host › should work using "local-ip" host and "auto" port ───── [chromium] › host.test.js:50:5 › host › should work using "local-ipv4" host and port as number ─ [chromium] › host.test.js:1
🎭 Playwright Run Summary
32 failed [chromium] › on-listening.test.js:57:3 › onListening option › should handle GET request to /listening/some/path route [chromium] › on-listening.test.js:92:3 › onListening option › should handle POST request to /listening/some/path route [chromium] › overlay.test.js:83:3 › overlay › should show a warning for initial compilation ──── [chromium] › overlay.test.js:129:3 › overlay › should show an error for initial compilation ──── [chromium] › overlay.test.js:175:3 › overlay › should show a warning and error for initial compilation [chromium] › overlay.test.js:227:3 › overlay › should show an ansi formatted error for initial compilation [chromium] › overlay.test.js:277:3 › overlay › should show a warning and error for initial compilation and protects against xss [chromium] › overlay.test.js:326:3 › overlay › should not show initially, then show on an error, then hide on fix [chromium] › overlay.test.js:408:3 › overlay › should not show initially, then show on an error, then show other error, then hide on fix [chromium] › overlay.test.js:518:3 › overlay › should not show initially, then show on an error and allow to close [chromium] › overlay.test.js:699:3 › overlay › should not show a warning when "client.overlay.warnings" is "false" [chromium] › overlay.test.js:743:3 › overlay › should not show warning when it is filtered ───── [chromium] › overlay.test.js:784:3 › overlay › should show warning when it is not filtered ───── [chromium] › overlay.test.js:837:3 › overlay › should show a warning when "client.overlay" is "true" [chromium] › overlay.test.js:888:3 › overlay › should show a warning when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:941:3 › overlay › should show a warning when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1036:3 › overlay › should not show an error when "client.overlay.errors" is "false" [chromium] › overlay.test.js:1080:3 › overlay › should not show error when it is filtered ────── [chromium] › overlay.test.js:1122:3 › overlay › should show error when it is not filtered ────── [chromium] › overlay.test.js:1175:3 › overlay › should show an error when "client.overlay" is "true" [chromium] › overlay.test.js:1226:3 › overlay › should show overlay when Trusted Types are enabled [chromium] › overlay.test.js:1290:3 › overlay › should show overlay when Trusted Types are enabled and the "require-trusted-types-for 'script'" header was used [chromium] › overlay.test.js:1407:3 › overlay › should show an error when "client.overlay.errors" is "true" [chromium] › overlay.test.js:1460:3 › overlay › should show an error when "client.overlay.warnings" is "true" [chromium] › overlay.test.js:1513:3 › overlay › should show a warning and hide them after closing connection [chromium] › overlay.test.js:1586:3 › overlay › should show an error after invalidation ──────── [chromium] › overlay.test.js:1646:3 › overlay › should show a warning after invalidation ─────── [chromium] › overlay.test.js:1706:3 › overlay › should show error for uncaught runtime error ─── [chromium] › overlay.test.js:1751:3 › overlay › should not show filtered runtime error ───────── [chromium] › overlay.test.js:1792:3 › overlay › should show error for uncaught promise rejection [chromium] › overlay.test.js:1839:3 › overlay › should not show filtered promise rejection ───── [chromium] › overlay.test.js:1882:3 › overlay › should show overlay when "Content-Security-Policy" is "default-src 'self'" was used 5 skipped 90 passed (6.2m)
🎭 Playwright Run Summary
29 failed [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "spdy" server › should handle GET request to index route (/) [chromium] › built-in-routes.test.js:123:5 › Built in routes › with simple config › should handle GET request to directory index and list all middleware directories [chromium] › built-in-routes.test.js:271:5 › Built in routes › with multi config › should handle GET request to directory index and list all middleware directories [chromium] › history-api-fallback.test.js:42:5 › historyApiFallback option › as boolean › should handle GET request to directory [chromium] › history-api-fallback.test.js:100:5 › historyApiFallback option › as object › should handle GET request to directory [chromium] › history-api-fallback.test.js:162:5 › historyApiFallback option › as object with static › should handle GET request to directory [chromium] › history-api-fallback.test.js:190:5 › historyApiFallback option › as object with static › should prefer static file over historyApiFallback [chromium] › history-api-fallback.test.js:255:5 › historyApiFallback option › as object with static set to false › historyApiFallback should work and ignore static content [chromium] › history-api-fallback.test.js:328:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites for index [chromium] › history-api-fallback.test.js:356:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites and shows index for unknown urls [chromium] › history-api-fallback.test.js:386:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect any other specified rewrites [chromium] › history-api-fallback.test.js:451:5 › historyApiFallback option › as object with the "verbose" option › request to directory and log [chromium] › history-api-fallback.test.js:522:5 › historyApiFallback option › as object with the "logger" option › request to directory and log [chromium] › history-api-fallback.test.js:590:5 › historyApiFallback option › in-memory files › should take precedence over static files [chromium] › host.test.js:50:5 › host › should work using "local-ip" host and port as number ─── [chromium] › host.test.js:126:5 › host › should work using "local-ip" host and port as string ── [chromium] › host.test.js:198:5 › host › should work using "local-ip" host and "auto" port ───── [chromium] › host.test.js:50:5 › host › should work using "local-ipv4" host and port as number ─ [chromium] › host.test.js:1
🎭 Playwright Run Summary
28 failed [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "spdy" server › should handle GET request to index route (/) [chromium] › built-in-routes.test.js:123:5 › Built in routes › with simple config › should handle GET request to directory index and list all middleware directories [chromium] › built-in-routes.test.js:271:5 › Built in routes › with multi config › should handle GET request to directory index and list all middleware directories [chromium] › history-api-fallback.test.js:42:5 › historyApiFallback option › as boolean › should handle GET request to directory [chromium] › history-api-fallback.test.js:100:5 › historyApiFallback option › as object › should handle GET request to directory [chromium] › history-api-fallback.test.js:162:5 › historyApiFallback option › as object with static › should handle GET request to directory [chromium] › history-api-fallback.test.js:255:5 › historyApiFallback option › as object with static set to false › historyApiFallback should work and ignore static content [chromium] › history-api-fallback.test.js:328:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites for index [chromium] › history-api-fallback.test.js:356:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites and shows index for unknown urls [chromium] › history-api-fallback.test.js:386:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect any other specified rewrites [chromium] › history-api-fallback.test.js:451:5 › historyApiFallback option › as object with the "verbose" option › request to directory and log [chromium] › history-api-fallback.test.js:522:5 › historyApiFallback option › as object with the "logger" option › request to directory and log [chromium] › history-api-fallback.test.js:590:5 › historyApiFallback option › in-memory files › should take precedence over static files [chromium] › host.test.js:50:5 › host › should work using "local-ip" host and port as number ─── [chromium] › host.test.js:126:5 › host › should work using "local-ip" host and port as string ── [chromium] › host.test.js:198:5 › host › should work using "local-ip" host and "auto" port ───── [chromium] › host.test.js:50:5 › host › should work using "local-ipv4" host and port as number ─ [chromium] › host.test.js:126:5 › host › should work using "local-ipv4" host and port as string [chromium] › host.test.js:198:5 › host › should work using "local-ipv4" host and "a
🎭 Playwright Run Summary
29 failed [chromium] › allowed-hosts.test.js:1302:7 › allowed hosts › check host headers › should always allow value from the `host` options if options.allowedHosts is auto [chromium] › app.test.js:59:9 › app option › should work using "express" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "express" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect" application and "spdy" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "http" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "https" server › should handle GET request to index route (/) [chromium] › app.test.js:59:9 › app option › should work using "connect (async)" application and "spdy" server › should handle GET request to index route (/) [chromium] › built-in-routes.test.js:123:5 › Built in routes › with simple config › should handle GET request to directory index and list all middleware directories [chromium] › built-in-routes.test.js:271:5 › Built in routes › with multi config › should handle GET request to directory index and list all middleware directories [chromium] › history-api-fallback.test.js:42:5 › historyApiFallback option › as boolean › should handle GET request to directory [chromium] › history-api-fallback.test.js:100:5 › historyApiFallback option › as object › should handle GET request to directory [chromium] › history-api-fallback.test.js:162:5 › historyApiFallback option › as object with static › should handle GET request to directory [chromium] › history-api-fallback.test.js:190:5 › historyApiFallback option › as object with static › should prefer static file over historyApiFallback [chromium] › history-api-fallback.test.js:255:5 › historyApiFallback option › as object with static set to false › historyApiFallback should work and ignore static content [chromium] › history-api-fallback.test.js:328:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites for index [chromium] › history-api-fallback.test.js:356:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect rewrites and shows index for unknown urls [chromium] › history-api-fallback.test.js:386:5 › historyApiFallback option › as object with static and rewrites › historyApiFallback respect any other specified rewrites [chromium] › history-api-fallback.test.js:451:5 › historyApiFallback option › as object with the "verbose" option › request to directory and log [chromium] › history-api-fallback.test.js:522:5 › historyApiFallback option › as object with the "logger" option › request to directory and log [chromium] › history-api-fallback.test.js:590:5 › historyApiFallback option › in-memory files › should take precedence over static files [chromium] › host.test.js:50:5 › host › should work using "local-ip" host and port as number ─── [chromium] › host.test.js:126:5 › host › should work using "local-ip" host and port as string ── [chromium] › host.test.js:198:5 › host › should work using "local-ip" host and "auto" port ───── [chromium] › host.test.js:50:5 › host › should work using "local-ipv4" host and port as number ─ [chromium] › host.test.js:1