Repository navigation
test: answer favicon requests in the test server with 204 - #43772
Merged
Dmitry Gozman (dgozman) merged 1 commit intoOct 30, 2026
Merged
Conversation
Headless Chrome and Edge request /favicon.ico after a load and log the 404 as a console error. Chrome remembers the 404 for the rest of the browser lifetime, so in a full run only the first test of a worker gets it, but TZ-006, CL-017, NA-085 and RO-157 fail when they run alone with Chrome.
Contributor
Test results for "tests 1"23593 passed, 707 skipped Merge workflow run. |
Contributor
Test results for "MCP"5194 passed, 616 skipped Merge workflow run. |
Dmitry Gozman (dgozman)
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/favicon.icoafter a load and log the 404 as a console error. Chrome remembers the 404 for the rest of the browser lifetime, so in CI only the first test of each worker gets it.PWTEST_CHANNEL=chrome, and the Java port, which starts more browsers, hits this in CI./favicon.icowith 204 when no route handles it.