We have a number of failure groups for various reasons, some expected, others not so much. Using a separate issue to track these parity issues more closely than #11313

• pwa (expected, we have planned non-support for http-redirect, fewer passes means fewer requests to server)
• offline (expected, we have planned non-support for http-redirect, fewer passes means fewer requests to server)
• Stacks artifact is sometimes empty core(fr): parity on Stacks and FullPageSnapshot gatherers #12907
• Number of 404 requests is different on dbw core(fr): parity on Stacks and FullPageSnapshot gatherers #12907
• TTI quiet window can't be found on redirects-single-server / metrics core(fr): override quiet windows for observed performance #12873
• non-200 status does not produce a report on seo-status-403 core(fr): align navigation failure behavior #12862
• viewport is different on seo-tap-targets core(fr): parity on Stacks and FullPageSnapshot gatherers #12907
• infinite loop hangs LH on errors-infinite-loop core(fr): add protocol timeout to session #12913
• screenshot node IDs changed tests(fr): convert screenshot expectations #12912
• oopif support core(fr): collect OOPIF network data #12992

When this is complete, expected --invert-match pwa offline