Network june

[MikhailTryakhov]

Description

Finally azure networking functionality release!!!

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
  • the markdown help files have been regenerated using the commands listed here

[msJinLei]

@MikhailTryakhov Please fix the test failure

[MikhailTryakhov]

@msJinLei I'm a bit confused there... Copying from one of required tests...

  Total tests: 22
       Passed: 22
   Total time: 11.7885 Seconds
/home/vsts/work/1/s/artifacts/after.Azure.PowerShell.sln.targets(4,5): error MSB4181: The "MSBuild" task returned false but did not log an error. [/home/vsts/work/1/s/artifacts/Azure.PowerShell.sln] [/home/vsts/work/1/s/build.proj]
/home/vsts/work/1/s/build.proj(269,5): error MSB3073: The command "dotnet test /home/vsts/work/1/s/artifacts/Azure.PowerShell.sln --filter "AcceptanceType=CheckIn&RunType!=DesktopOnly" --configuration Debug --framework netcoreapp2.1 --logger trx --results-directory "/home/vsts/work/1/s/artifacts//TestResults"" exited with code 1.
/home/vsts/work/1/s/build.proj(289,5): error : Test failures occurred, check the files in artifacts/TestResults
##[error]Error: The process '/opt/hostedtoolcache/dotnet/dotnet' failed with exit code 1
Info: Azure Pipelines hosted agents have been updated to contain .Net Core 3.x (3.1) SDK/Runtime along with 2.1. Unless you have locked down a SDK version for your project(s), 3.x SDK might be picked up which might have breaking behavior as compared to previous versions. 
Some commonly encountered changes are: 
If you're using `Publish` command with -o or --Output argument, you will see that the output folder is now being created at root directory rather than Project File's directory. To learn about more such changes and troubleshoot, refer here: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshooting
##[error]Dotnet command failed with non-zero exit code on the following projects : 
Finishing: Test 

Where is it from? how is it possible to have all tests ran successfully and have a magic failure after that? Can you please help me to investigate?

[MikhailTryakhov]

Fixed version in dependant project, please review?

[MikhailTryakhov]

@msJinLei solved

[msJinLei]

@msJinLei solved

Please fix the failed test case.

[MikhailTryakhov]

Guys, Again completely the same for the 2nd weeks in a row @msJinLei
I don't understand what is an issue AFTER successful running of the tests...
Can you please help to merge it or to finally figure out what's happened?

[msJinLei]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[VeryEarly]

Guys, Again completely the same for the 2nd weeks in a row @msJinLei
I don't understand what is an issue AFTER successful running of the tests...
Can you please help to merge it or to finally figure out what's happened?

Those test failures are caused by network module referenced by scenario tests in other modules, skip API version check in those modules could be the fix.

[azure-pipelines]

Command 'run

' is not supported by Azure Pipelines.

Supported commands

• help:
• Get descriptions, examples and documentation about supported commands
• Example: help "command_name"
• list:
• List all pipelines for this repository using a comment.
• Example: "list"
• run:
• Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
• Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
• where:
• Report back the Azure DevOps orgs that are related to this repository and org
• Example: "where"

See additional documentation.

[MikhailTryakhov]

As per contact with Yabo Hu, it's definitely time to merge it! Please let's do it!

[msJinLei]

Your patch contains the feature code changes of Compute and KeyVault.
Could you rebase/merge the latest master to have them removed from change list?
I try to merge the latest master and unnecessary changes are removed https://github.com/Azure/azure-powershell/pull/12857/files.

[MikhailTryakhov]

@msJinLei can you please finallly merge it and that's all?

[msJinLei]

@msJinLei can you please finallly merge it and that's all?

Your patch contains the feature code changes of Compute and KeyVault. It is because you don't merge the latest master.
Please rebase/merge the latest master to have them removed from change list.