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

Added OS and Bit Specific tags to accordingly .csproj files. #637

Merged
merged 1 commit into from
Dec 13, 2019
Merged

Added OS and Bit Specific tags to accordingly .csproj files. #637

merged 1 commit into from
Dec 13, 2019

Conversation

ivdiazsa
Copy link
Member

@ivdiazsa ivdiazsa commented Dec 6, 2019

As part of the test build infrastructure changes, tags determining OS-specific, Bitness-Specific, and other behaviors will be added to the necessary project files. This will be used in the future by an include/exclude mechanism for builds. By looking into preprocessor directives in the test files, this PR adds the first two tags mentioned before.

Copy link
Member

@AaronRobinsonMSFT AaronRobinsonMSFT left a comment

Choose a reason for hiding this comment

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

Looks good. Thanks. Has a comprehensive list of traits been defined somewhere?

@ivdiazsa
Copy link
Member Author

ivdiazsa commented Dec 6, 2019

Looks good. Thanks. Has a comprehensive list of traits been defined somewhere?

Formally, no. In the discussions held with @VSadov, @jashook, and @trylek, we came up with other possibilities, such as GCLongRunning and GCStressIncompatible, but those ought to be treated with care. So, the decision was to just formalize the two I added and, as the include/exclude mechanism is developed, adding them as necessary.

@ivdiazsa ivdiazsa requested a review from jashook December 6, 2019 23:26
Copy link
Member

@trylek trylek left a comment

Choose a reason for hiding this comment

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

LGTM, thank you!

@@ -11,4 +11,7 @@
<ItemGroup>
<Compile Include="$(MSBuildProjectName).cs" />
</ItemGroup>
<ItemGroup>
Copy link
Member

Choose a reason for hiding this comment

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

Is this supposed to be the TagList ? I actually like TraitTags more, just want to confirm this is intentional use of the name.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, TraitTags is the name currently given to the taglist.

Copy link
Member

Choose a reason for hiding this comment

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

I must admit I give a damn about the actual identifier. As you two guys are mostly working on this now and no work has been done to support these in the actual test projects AFAIK, I guess you two just figure out whatever naming you're happy with.

Copy link
Member

Choose a reason for hiding this comment

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

Me too :-) . Just wanted to make sure this is not something different.
TraitTags sounds good to me.

Copy link
Member

@VSadov VSadov left a comment

Choose a reason for hiding this comment

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

LGTM

@ivdiazsa ivdiazsa merged commit 9495098 into dotnet:master Dec 13, 2019
@ivdiazsa ivdiazsa deleted the TestTagsForFiltering branch December 13, 2019 00:40
@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-coreclr test-enhancement Improvements of test source code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants