Skip to content

[Windows build perf] Tasks with no inputs should not be executed remotely #19600

Open
@emaf

Description

@emaf

Steps to Reproduce

As running tasks remotely adds ~200ms to the execution, we should avoid executing remotely tasks that have no inputs and that won't end up doing anything on the Mac in that case.

There might be more, but these are the ones I've found so far:

  • GetFileSystemEntries when no DirectoryPath was specified
  • FilterStaticFrameworks when no FrameworkToPublish was specified
  • GetFullPaths when Items is empty
  • Copy when SourceFiles is empty
  • CoreMLCompiler when there are no models

Expected Behavior

Actual Behavior

Environment

Version information

Build Logs

Example Project (If Possible)

Metadata

Metadata

Assignees

No one assigned

    Labels

    msbuildIssues affecting our msbuild tasks/targetsperformanceIf an issue or pull request is related to performancewindows-onlyThe issue only occur on Windows

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions