PR Summary

• Update Linux daily build to run tests in a single agent
• Collect CLR traces in Windows daily build
  • Download the CAP utility package from https://pscoretestdata.blob.core.windows.net/dotnet-cap/windows.zip
  • Start trace collection before test run
  • Stop trace collection after test run

Build using linux-daily.yml: https://dev.azure.com/powershell/PowerShell/_build/results?buildId=54399&view=results
Build using windows-daily.yml: https://dev.azure.com/powershell/PowerShell/_build/results?buildId=54125&view=results

Trace collection in Linux daily build is not included in this PR. I got some issues installing perfcollect in the CI environment.
I will submit a separate PR after resolving the issues.

Background

This is to implement CLR Customer Assistance Program (CAP):

The CLR CAP was created with two goals in mind: proactively help partner teams resolve CLR related issues and help the our team gain better insights into how the CLR is performing on first party services. The CLR CAP is 100% based on the collection and analysis of events in CLR (ETW in Windows for .NET Frameworks and EventPipe technology for .NET Core runtime).

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).