dotnet/runtime

Update BenchI and BenchF benchmarks to validate results

Open

#5,049 建立於 2016年2月2日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)C# (17,886 star) (5,445 fork)batch import
Hackathonarea-CodeGen-coreclrgood first issuehelp wantedin-prtest-bug

描述

These benchmarks (tests/src/JIT/performance/codequality) don't all consistently check for correctness of results. They've been useful in the past without it but would be a nice additional validation measure to do this.

category:correctness theme:testing skill-level:beginner cost:medium impact:small

貢獻者指南

技術棧
csharp
領域
testing
議題類型
test
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C# programming basicsUnderstanding of unit testing concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
Examine the benchmarks in tests/src/JIT/performance/codequality to understand their structure. Currently, they may not check for correctness of results. Add assertions to verify the output matches expected values. Refer to existing test patterns in the repository for guidance. No linked PRs or recent comments.
Update BenchI and BenchF benchmarks to validate results · dotnet/runtime#5049 | Good First Issue