Repository navigation
Conversation
Collaborator
|
What's the context for this PR? |
Collaborator
Author
@IvanBM18 Found some 404 errors on aluminum fuzzers that uncover this bug. Adding context in the description |
dylanjew
reviewed
Oct 30, 2026
dylanjew
left a comment
Collaborator
There was a problem hiding this comment.
Thanks! is there a bug for this?
And is there a way to run the test syncer job to verify it as well? If you change it to just log the error this is less critical.
dylanjew
reviewed
Oct 30, 2026
Collaborator
Author
The bug is in b/570581291 |
Add static HTTP_ALIASES in http_server.py for legacy Gecko Mochitest, Blink, and WebKit test-server mounts, verify all alias target directories exist before zipping web_tests.zip in chrome_tests_syncer.py, strip URL queries/fragments before resolving local paths, and log 404 misses at INFO level.
Xeicker
force-pushed
the
fix-blackbox-http-aliases
branch
from
October 30, 2026 21:20
c5c3a60 to
5ddd386
Compare
This branch has not been deployed
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.
Context:
When blackbox browser fuzzing (E.g.
inferno_layout_test_fuzzer) serves corpus testcases from web_tests.zip over BotHTTPServer (e.g., on Android emulators where FUZZ_DATA is served via HTTP), root-relative test-harness URLs (/tests/SimpleTest/..., /MochiKit/..., /js-test-resources/..., etc.) and WPT ?pipe= query URLs fail with 404 (Could not find an absolute path for ...). Missing harness scripts (SimpleTest.js, js-test.js) abort testcase JS execution with ReferenceErrorWhat this fixes
Resolves 404s when
BotHTTPServerserves legacy Mochitest, Blink, and WebKit test-harness paths (/tests/SimpleTest/...,/MochiKit/...,/js-test-resources/..., etc.) and?pipe=query URLs fromweb_tests.zip, with a directory check inchrome_tests_syncer.pyso upstream renames fail loudly at sync time.Why not reuse Chromium's native web-test server setup: Chromium's
run_web_tests(apache_http.py/wptserve) runs separate servers/ports per suite, which collides with ClusterFuzz serving Blink, WPT, WebKit, Gecko, data bundles, and generated testcases from a singleBotHTTPServerport (where paths like/resources/overlap across suites) and relying onhttp_server.get_absolute_testcase_file()in Python to package crash dependencies.Testing:
http_server_test.py,chrome_tests_syncer_test.py) andbutler.py lint.inferno_layout_test_fuzzeron an Android emulator blackbox job (413→0aliased/query 404s;418→0WARNING404s).