Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug: unable to propagate --concurrent setting to .NET Core executables via dotnet nbench #250

Closed
Aaronontheweb opened this issue Jul 23, 2018 · 0 comments
Closed

Bug: unable to propagate --concurrent setting to .NET Core executables via dotnet nbench #250

Aaronontheweb opened this issue Jul 23, 2018 · 0 comments
Labels
benchmark-execution Execution and discovery engine for the NBench SDK bug netcore .NET Core runtime support
Milestone
1.2.2

Comments

@Aaronontheweb
Copy link
Member

Unable to pass the --concurrent flag down to the underlying NBench executable. Should check to see if there are also issues with --trace and some of the other flags we intend to pass.
@Aaronontheweb Aaronontheweb added bug benchmark-execution Execution and discovery engine for the NBench SDK netcore .NET Core runtime support labels Jul 23, 2018
@Aaronontheweb Aaronontheweb added this to the 1.2.2 milestone Jul 23, 2018
Aaronontheweb added a commit that referenced this issue Jul 24, 2018
@Aaronontheweb
Merge pull request #251 from Aaronontheweb/fix-250-params
d1e2444 
close #250 - fix params
This was referenced Jul 24, 2018
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
benchmark-execution Execution and discovery engine for the NBench SDK bug netcore .NET Core runtime support
Projects
None yet
Milestone
1.2.2
Development

No branches or pull requests
1 participant
@Aaronontheweb