Skip to content

Update docs after repos merge#1132

Merged
adamsitnik merged 16 commits intodotnet:masterfrom
adamsitnik:updateDocsAfterReposMerge
Jan 17, 2020
Merged

Update docs after repos merge#1132
adamsitnik merged 16 commits intodotnet:masterfrom
adamsitnik:updateDocsAfterReposMerge

Conversation

@adamsitnik
Copy link
Member

Fixes #990

/// benchmarks belonging to this category are executed for CoreFX CI jobs
/// </summary>
public const string CoreFX = "CoreFX";
public const string Libraries = "CoreFX";
Copy link
Member Author

Choose a reason for hiding this comment

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

@billwert @DrewScoggins I have changed the folder structure and renamed the categories (CoreFX -> Libraries, CoreCLR -> Runtime) but did not change the... values of the constants.

So in the code we now have:

[BenchmarkCategory(Categories.Runtime, Categories.Libraries)]

But the values remained CoreFX and CoreCLR. I did that to make sure that we don't change the real categories names which I assume would affect the naming in the Reporting Service. Please let me know if this is good or bad idea.

Copy link
Contributor

Choose a reason for hiding this comment

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

@DrewScoggins Can you confirm whether or not category is part of test identity? I think it is, but this leads to interesting questions (such as if someone adds a category will they break us)?

I think this is a fine change for now, leaving the values the same. I'm a little worried that we're going to have the impetus to change these again the next time we rename teams, and would like to avoid that.

Copy link
Member

Choose a reason for hiding this comment

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

We store the test category in a side table, so it is not part of the main identity. Updating the category for the test will just add this category as one of many that are applied to the test. So this would not break anything in the reporting side.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for the explanation. I've changed the values as well. So now CoreCLR and CoreFX names are not really used anymore

*.dbmdl
*.dbproj.schemaview
*.jfm
*.pfx
Copy link
Member Author

Choose a reason for hiding this comment

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

we actually use pfx files in this repo (certificates used by networking benchmarks)

Copy link
Contributor

@billwert billwert left a comment

Choose a reason for hiding this comment

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

Overall looks pretty good. Left a handful of comments/questions.

/// benchmarks belonging to this category are executed for CoreFX CI jobs
/// </summary>
public const string CoreFX = "CoreFX";
public const string Libraries = "CoreFX";
Copy link
Contributor

Choose a reason for hiding this comment

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

@DrewScoggins Can you confirm whether or not category is part of test identity? I think it is, but this leads to interesting questions (such as if someone adds a category will they break us)?

I think this is a fine change for now, leaving the values the same. I'm a little worried that we're going to have the impetus to change these again the next time we rename teams, and would like to avoid that.

@adamsitnik adamsitnik requested a review from billwert January 16, 2020 20:13
@adamsitnik
Copy link
Member Author

@billwert Thank you for the review! I've applied all the suggestions. PTAL

Copy link
Member

@DrewScoggins DrewScoggins left a comment

Choose a reason for hiding this comment

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

LGTM

@adamsitnik
Copy link
Member Author

@billwert I've addressed all your feedback, I am going to merge this PR now to work on #1000 and be done with updating docs.

@adamsitnik adamsitnik merged commit 8aed638 into dotnet:master Jan 17, 2020
@adamsitnik adamsitnik deleted the updateDocsAfterReposMerge branch January 17, 2020 10:57
@billwert
Copy link
Contributor

LGTM! (Sorry, was OOF sick yesterday.)

Copy link
Member

@danmoseley danmoseley left a comment

Choose a reason for hiding this comment

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

LGTM

@adamsitnik
Copy link
Member Author

@filipnavara as far as I remember you are using categories names to filter the benchmarks when running them for Mono. After this PR got merged you should change your filters:

  • corefx -> libraries
  • coreclr -> runtime

@filipnavara
Copy link
Member

@adamsitnik Thanks for heads up. I already noticed my builds were failing and fixed it up yesterday. :)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update all the docs once CoreFX and CoreCLR are merged into dotnet/runtime

5 participants