Update (remove most) most of CLRTestKind, GenerateRunScript, RestorePackages#89696
Update (remove most) most of CLRTestKind, GenerateRunScript, RestorePackages#89696trylek merged 4 commits intodotnet:mainfrom
Conversation
|
Tagging subscribers to this area: @dotnet/area-system-reflection-metadata Issue Detailsnull
|
|
@trylek @jkoritzinsky This is fallout from staring at msbuild properties too long for merged groups. cc @dotnet/jit-contrib @Maoni0 @cshung @mrsharm I'm a bit concerned that the checkin gate doesn't provide complete coverage so would welcome additional tests to run. |
|
/azp run runtime-coreclr outerloop, runtime-extra-platforms |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
One little static check on the contents of the diff: The conditional updates are the change to the default in Directory.Build.targets. The PropertyGroup removals are intended (not unchecked) removals of (now) empty groups. |
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsI came across these while looking at the set of properties in order to generate some error checking for merged groups. As best as I can tell, most of these are very old uses that likely have had the test system changed from under them. They cause confusion when encountered.
|
trylek
left a comment
There was a problem hiding this comment.
Thanks Mark for cleaning this up!
|
Based on offline discussion with Mark I have rebased this change against latest main and I plan to retest it and merge it in once it passes as the start of my quality week activities as Mark has fully switched over to GC work. |
|
/azp run runtime-extra-platforms |
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Runtime and outerloop runs are clean and for the runtime-extra-platforms I haven't found any issues different from a previous run, merging in. |
|
We stopped running the SharedLibrary test after this change. I'm putting back the ClrTestKind for this test in #91356 but I do wonder if there's any other test we stopped running by dropping ClrTestKind. |
|
This one happened because the test was marked OutputType==library and ClrTestKind=BuildAndRun. However, it looks like it depends on a native entry point (and CLRTestBatchPreCommands, etc.), so the managed part of the test is "library" but the overall project is an executable. I just did a scan of all proj files in that commit that removed BuildAndRun, and SharedLibrary is the only one of the ~30 that doesn't have OutputType==exe. |
I came across these while looking at the set of properties in order to generate some error checking for merged groups. As best as I can tell, most of these are very old uses that likely have had the test system changed from under them. They cause confusion when encountered.