dotnet/runtime

Update BenchI and BenchF benchmarks to validate results

Open

#5,049 opened on Feb 2, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
Hackathonarea-CodeGen-coreclrgood first issuehelp wantedin-prtest-bug

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

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

Contributor guide

Research direction
Examine each benchmark in tests/src/JIT/performance/codequality, identify those lacking result validation, and implement checks to verify correctness.
Tech stack
csharp
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80