dotnet/BenchmarkDotNet

Simple API for path customization of BenchmarkDotNet.Artifact and job folders

Open

#377 opened on Mar 1, 2017

View on GitHub
 (15 comments) (5 reactions) (0 assignees)C# (11,415 stars) (1,054 forks)batch import
enhancementhelp wantedup-for-grabs

Description

Sometimes we have troubles with UnauthorizedAccessException (we don't have access to the current directories) or long paths. I think, it would be great to provide a nice API which allows to customzie BenchmarkDotNet working directory (which will contain all the generated files and folders).

Contributor guide

Tech stack
csharp
Domain
performancetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C# knowledgeBenchmarkDotNet basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the current artifact path handling in BenchmarkDotNet, specifically the code that generates the output directories. Suggest adding a configuration option or API method to allow users to set a custom working directory. Look at the issue comments for user requirements and potential implementation ideas.