-
Notifications
You must be signed in to change notification settings - Fork 293
Open
Labels
impact test coveragetest maybe disabled due to this issuetest maybe disabled due to this issue
Description
This tracking issue documents the set of performance tests disabled for WasmCoreCLR as implemented in PR #5135.
Summary
In PR #5135, the Categories.NoWasmCoreCLR attribute was added to 32 benchmarks across 14 files due to persistent timeouts exceeding the 20-minute limit during WasmCoreCLR BenchmarkDotNet (BDN) test runs. Temporarily disabling these tests enables CI stabilization and further investigation.
Disabled Benchmarks (via NoWasmCoreCLR):
- Burgers
- ByteMark
- ConsoleMandel
- LinqBenchmarks
- MandelBrot_7
- MDArray2
- MDInProd
- MDMulMatrix
- MDSqMtx
- Perf_StreamWriter
- RayTracerBench
- SeekUnroll
- Sort
- SortingTests
For further details, refer to CI build links:
- Wasm CoreCLR test timeout sample: https://dev.azure.com/dnceng/internal/_build/results?buildId=2915976&view=results
clr-log1.txt
clr-log2.txt
clr-log3.txt
clr-log4.txt
clr-log5.txt
- Successful NoWasmCoreCLR test run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2916496&view=results
Next Steps
- Track the impact on performance coverage.
- Revisit these benchmarks after future improvements or investigations into the WasmCoreCLR runtime performance and CI stability.
- See PR #5135 discussion for context and links to excluded files.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
impact test coveragetest maybe disabled due to this issuetest maybe disabled due to this issue