Skip to content

Consider running .NET Framework tests on build agent instead of on Helix #53924

Open
@ViktorHofer

Description

@ViktorHofer

Using a batched build for measurements: https://dnceng.visualstudio.com/public/_build/results?buildId=1178181&view=logs&j=be745447-21d7-5722-3f01-3e5709978455&t=80dd1e14-d738-5614-f259-51a0bdabd48b

Building .NET Framework libraries and tests currently takes 6 minutes. Running the tests on Helix takes 25 minutes and presumably the time it takes to run the .NET Framework tests (either sequentially or in parallel) is far less than that. As .NET Framework tests already run on the same OS as they are built on (Windows 10 x64/x86) the value of using Helix here is questionable.

Reducing the amount of Helix usage helps both us in regards to build times, dependencies and with that reliability and the core-eng team in regards to machine consumption. If I'm not mistaken, the uploading of the test results would need to be taken care of in the yml but that should be straightforward as that's a functionality on the common path.

cc @safern @Anipik @ericstj

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions