Update the Blazor WebAssembly perf benchmarks to use a different docker image #55813
Labels
area-blazor
Includes: Blazor, Razor Components
feature-blazor-wasm
This issue is related to and / or impacts Blazor WebAssembly
Perf
task
Milestone
The Blazor WebAssembly performance benchmarks have been making our builds yellow for some time now, so we've disabled them as of #55812.
The fix is either to add the
selenium/standalone-chrome
Docker image to MCR or use a different image and set up Chrome and Selenium manually in the Dockerfile. The latter may end up being the better short-term solution.The text was updated successfully, but these errors were encountered: