[release/5.0.1xx-preview8] Update dependencies from microsoft/vstest

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/microsoft/vstest

• Subscription: 7ed3ff5b-1270-4370-3cc2-08d824643728
• Build: 20200730-03
• Date Produced: 7/30/2020 1:01 PM
• Commit: ddb755f58160c0e7fab50964d665be1bf47ff579
• Branch: refs/heads/master

• Updates:
  • Microsoft.NET.Test.Sdk: from 16.8.0-preview-20200730-02 to 16.8.0-preview-20200730-03

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[Anipik]

@ViktorHofer any particular reason behind the ask mode label ? do we need to bring it to tactics before merging ?

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[ViktorHofer]

It's a tooling change. Don't we need to?

[Anipik]

We don't do this for dependency updates. The original commit that is triggering the dependency updates should be approved by tactics

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[ViktorHofer]

We don't do this for dependency updates. The original commit that is triggering the dependency updates should be approved by tactics

That's news to me. I have never heard of Tactics approving commits in Microsoft/vstest. VSTest currently flow bits from their master branch which means that Tactics would need to approve any master commit.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[Anipik]

That's news to me. I have never heard of Tactics approving commits in Microsoft/vstest. VSTest currently flow bits from their master branch which means that Tactics would need to approve any master commit.

I think u r right here. I think We dont generally seek approval for dependency updates from VSTest, because they are version updates with no real commit sha changes.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[ViktorHofer]

because they are version updates with no real commit sha changes.

Unsure what you mean by "no real commit sha changes". Microsoft/vstest is very much alive, we have a team that is actively working on features in the repository.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[Anipik]

Unsure what you mean by "no real commit sha changes".

We are already consuming the latest commit here #12711
Not sure if this pr was created bcoz they push a daily new package.

[ViktorHofer]

We are already consuming the latest commit here #12711

This isn't the same change, it's missing the macOS env var hang dump support. @nohwnd isn't flowing VSTest master into P8
without any approval super risky? Should we change that?

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[Anipik]

@nohwnd isn't merging all master commits into P8 super risky? Should we change that?

did u mean master and P8 of the sdk repo ?

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Debug), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[nohwnd]

@ViktorHofer disabled, we now push from master only to VS Master channel, which would end up in as a PR against dotnet/sdk master.

If there are more updates needed for P8 we will need to do that via rel/16.8 branch in vstest.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ Standard Merge Policies Unsuccessful checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Darwin Build_Release)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.

[ViktorHofer]

/azp run dotnet-sdk-public-ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dotnet-maestro]

Auto-Merge Status

This pull request has been merged because the following merge policies have succeeded.

• ✔️ Standard Merge Policies Succeeded - Successful checks: dotnet-sdk-public-ci, dotnet-sdk-public-ci (Build Windows_NT_TestAsTools Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Release), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Release), dotnet-sdk-public-ci (Build Darwin Build_Release), dotnet-sdk-public-ci (Build Windows_NT Build_Debug), dotnet-sdk-public-ci (Build Ubuntu_16_04 Build_Debug), dotnet-sdk-public-ci (Build Windows_NT_FullFramework Build_Debug), dotnet-sdk-public-ci (Build Darwin Build_Debug)
• ✔️ Standard Merge Policies Succeeded - No reviews have requested changes.
• ✔️ Standard Merge Policies Succeeded - No version downgrade detected.