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.

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

1799 adding resume arg #2164

Merged
merged 11 commits into from Oct 26, 2022
Merged

1799 adding resume arg #2164

merged 11 commits into from Oct 26, 2022

Conversation

melias
Copy link
Contributor

@melias melias commented Oct 19, 2022

No description provided.

@dnfadmin
Copy link

dnfadmin commented Oct 19, 2022

CLA assistant check
All CLA requirements met.

Copy link
Member

@adamsitnik adamsitnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@melias thank you for your contribution! PTAL at my comments.

src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs Outdated Show resolved Hide resolved
src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs Outdated Show resolved Hide resolved
@melias melias requested review from adamsitnik and timcassell and removed request for adamsitnik and timcassell October 21, 2022 10:46
src/BenchmarkDotNet/Running/BenchmarkRunnerClean.cs Outdated Show resolved Hide resolved
foreach (var benchmarkRunInfo in supportedBenchmarks) // we run them in the old order now using the new build artifacts
{
if (benchmarkRunInfo.Config.Options.IsSet(ConfigOptions.Resume))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we can assume that if parsedIdToResume was parsed (at least one of the configs defined it), we are using it as source of truth

Suggested change
if (benchmarkRunInfo.Config.Options.IsSet(ConfigOptions.Resume))
if (parsedIdToResume > 0)

Copy link
Member

@adamsitnik adamsitnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

During manual testing I've found some edge case bugs, but since we don't have much time (the hackathon ends today) I've sent some minor polishing fixes directly to your fork.

Thank you for your contribution @melias !

@melias
Copy link
Contributor Author

melias commented Oct 26, 2022

During manual testing I've found some edge case bugs, but since we don't have much time (the hackathon ends today) I've sent some minor polishing fixes directly to your fork.

Thank you for your contribution @melias !

Thanks @adamsitnik
I'm happy to contribute and I will continue to help :)

@YegorStepanov
Copy link
Contributor

Is this repository participating in hacktoberfest?

image

Look at dotnet/runtime#76515.

It looks like you need to add a label to the repository:
image

@adamsitnik
Copy link
Member

Is this repository participating in hacktoberfest?

We are currently participating in https://code.devexperts.com/event/openhack22

It looks like you need to add a label to the repository:

I don't have permissions to do that, @AndreyAkinshin could you please add the label?

@YegorStepanov in the past we had to apply Hacktoberfest labels to issues/PRs in order for the contributions to count. Please let me know if I should add these labels to any of your PRs

@adamsitnik adamsitnik merged commit 0f7eb25 into dotnet:master Oct 26, 2022
@adamsitnik adamsitnik added this to the v0.13.3 milestone Oct 26, 2022
@AndreyAkinshin
Copy link
Member

I don't have permissions to do that, @AndreyAkinshin could you please add the label?

Done.

@YegorStepanov
Copy link
Contributor

YOUR PR/MRS MUST BE IN A REPO TAGGED WITH THE “HACKTOBERFEST” TOPIC, OR HAVE THE “HACKTOBERFEST-ACCEPTED” LABEL.

You can remove Hacktoberfest from issues, because they don't count anymore.
https://github.com/dotnet/BenchmarkDotNet/issues?q=is%3Aissue+is%3Aopen+label%3AHacktoberfest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants