Disable flaky Chromium test NormalRendererMetricsAreNotMapped on Linux MSan (#35237)

Disable Chromium test NormalRendererMetricsAreNotMapped on Linux MSan

This is an upstream Chromium test with a 2.9% flake rate (LUCI
Analysis, 30 days). Chromium has already disabled it on ChromeOS MSan
(crbug.com/491012584). The test asserts zero samples for the renamed
Webium histogram in a non-initial-WebUI renderer, but pending
histograms from the browser's initial WebUI startup process can leak
into the measurement under slow MSan execution.

No Brave modifications exist in chrome/browser/ui/waap/.

Resolves https://github.com/brave/brave-browser/issues/54031
This commit is contained in:
Netzenbot
2026-04-04 09:13:27 -04:00
committed by GitHub
parent 0d1acf07f9
commit 872c8a2fd5
@@ -23,3 +23,13 @@
# for the same reason.
# https://github.com/brave/brave-browser/issues/54053
-DevToolsExtensionHostsPolicyTest.CantInspectBlockedHost
# Upstream Chromium test. Known upstream flake (2.9% flake rate over 30 days
# per LUCI Analysis). Already disabled on ChromeOS MSan upstream
# (crbug.com/491012584). The test expects zero samples for the renamed
# histogram Webium.Navigation.DocumentLoader.DidCommitNavigation in a
# non-initial-WebUI renderer, but pending histograms from the browser's own
# initial WebUI startup process can leak into the measurement under slow MSan
# execution. No Brave modifications in chrome/browser/ui/waap/.
# https://github.com/brave/brave-browser/issues/54031
-InitialWebUIMetricsMappingBrowserTest.NormalRendererMetricsAreNotMapped