[tests] Retain OutDir for ioslike tests#82313
Conversation
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue Details
|
|
/azp run runtime-ioslike, runtime-maccatalyst |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run runtime-ioslike, runtime-maccatalyst |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run runtime-ioslike, runtime-maccatalyst |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Across 6 runs of runtime-ioslike not from this PR, the average disk usage (Change in Avail Column between before build and after build) Across the 2 runs of runtime-ioslike from this PR, the average disk usage tvOS lanes are impacted more because they build 197 workitems, whereas iOS lanes build just 4 workitems, so the tvOS capacity change is the metric to focus on. |
40f374a to
f8ce0b9
Compare
|
/azp run runtime-ioslike, runtime-ioslikesimulator, runtime-maccatalyst |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Looks like osx.1200.amd64.open has issues, will rerun the startuphook functional test again after the problem is resolved to verify that the original issue is resolved. |
|
/azp run runtime-ioslike, runtime-ioslikesimulator, runtime-maccatalyst |
|
Azure Pipelines successfully started running 3 pipeline(s). |
$(OutDir)was removed in the ioslike tests build for the purpose of saving space, however some projects that include references will need assemblies in the$(OutDir)directory for theCoreCompiletarget. In the libraries tests, there is a workaround for this. This PR examines whether or not the$(OutDir)needs to be removed, using a metric of <100MB remaining when it is not removed to determine that it should continue to be removed.