Skip to content

Conversation

@v-wuzhai
Copy link
Contributor

No description provided.

dotnet-maestro bot and others added 30 commits October 14, 2022 12:00
…013.4

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22513.4
…014.3

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22514.3
…031.4

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22531.4
…107.1

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22557.1
…108.4

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22558.4
…1114.1

Microsoft.Build , Microsoft.Build.Localization
 From Version 17.5.0-preview-22561-03 -> To Version 17.5.0-preview-22564-01
…113.3

Microsoft.SourceBuild.Intermediate.fsharp , Microsoft.FSharp.Compiler
 From Version 7.0.1-beta.22561.2 -> To Version 7.0.1-beta.22563.3
…7b7-4504-81ff-8164ad62a4a8

[release/7.0.2xx] Update dependencies from dotnet/msbuild
…eed-4bbb-8075-40511483848d

[release/7.0.2xx] Update dependencies from dotnet/fsharp
Include ijwhost in DesignerRuntimeImplementationProjectOutputGroupOutput
This broke with changes related to #27199.
It's now possible to have multiple supported platform version items for the
same version.
Depending on whether we're using preview versions, some of the packages
may be downloaded by NuGet and have lowercased names, while at other
times they may be shipped in the packs folder and have mixed case.
…orm-version

Fix TargetPlatformVersion normalization for Windows
…111.2

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22558.4 -> To Version 7.0.0-beta.22561.2
@vlada-shubina vlada-shubina added the Area-dotnet new the item is related to dotnet new command label Nov 22, 2022
@GangWang01
Copy link
Member

PR dotnet/templating#5223 is not ported to templating release/7.0.2xx. It causes different behaviors when dealing with disabled parameters as we recently found.

We need to change the approvals for the following tests when merging into main branch.

        [Theory]
        [InlineData("TestAssets.TemplateWithConditionalParameters|--paramA|valA", "A")]
        [InlineData("TestAssets.TemplateWithConditionalParameters|--paramA|valA|--paramB|valB", "AB")]
        //[InlineData("TestAssets.TemplateWithConditionalParameters|--paramA|valA|--paramB|valB|--A_enabled", "AB")]
        public Task CannotInstantiateTemplate_WithDisabledParams(string parameters, string setName)

Approvals:

// value of paramA: placeholderA
// value of paramB: placeholderB

@vlada-shubina do we need to port PR dotnet/templating#5223 to templating release/7.0.2xx and adjust the test to resolve this problem, or just adjust the test for SDK main branch?

@vlada-shubina
Copy link
Member

PR dotnet/templating#5223 is not ported to templating release/7.0.2xx. It causes different behaviors when dealing with disabled parameters as we recently found.

We need to change the approvals for the following tests when merging into main branch.

        [Theory]
        [InlineData("TestAssets.TemplateWithConditionalParameters|--paramA|valA", "A")]
        [InlineData("TestAssets.TemplateWithConditionalParameters|--paramA|valA|--paramB|valB", "AB")]
        //[InlineData("TestAssets.TemplateWithConditionalParameters|--paramA|valA|--paramB|valB|--A_enabled", "AB")]
        public Task CannotInstantiateTemplate_WithDisabledParams(string parameters, string setName)

Approvals:

// value of paramA: placeholderA
// value of paramB: placeholderB

@vlada-shubina do we need to port PR dotnet/templating#5223 to templating release/7.0.2xx and adjust the test to resolve this problem, or just adjust the test for SDK main branch?

dotnet/templating#5223 won't be ported to release/7.0.2xx, therefore please adjust the test.

@v-wuzhai v-wuzhai force-pushed the v-wuzhai/Merge702tomain branch 2 times, most recently from 7cc1502 to 942e12c Compare November 24, 2022 07:34
@v-wuzhai
Copy link
Contributor Author

@marcpopMSFT @dsplaisted It seems that some of the newly enabled test runs are failed in main.

@vlada-shubina
Copy link
Member

@v-wuzhai I merged the fix prepared by @GangWang01. There were tests failures in his PR but I don't think they are related to fix, also same failures were observed in this PR. Please let me know if you need any other assistance from templating team.

@vlada-shubina vlada-shubina removed the Area-dotnet new the item is related to dotnet new command label Nov 24, 2022
@nagilson
Copy link
Member

nagilson commented Nov 28, 2022

No, those failures seem related to something Marc was working on fixing.

@marcpopMSFT
Copy link
Member

Actually, I enabled all the cppcli tests. However, because cppcli doesn't support implicit versions, it has to target the same runtime as the SDK used in the tests. So in 7.0 these tests worked but they had to be updated to target 8.0 with this flow to main. I made the changes I think are needed. Let's see if the tests pass.

@v-wuzhai
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@v-wuzhai
Copy link
Contributor Author

##[error]Unhandled: ENOSPC: no space left on device, open 'D:\a_temp.taskkey'

@marcpopMSFT There seems to be no real error. Could we force to merge?

@marcpopMSFT
Copy link
Member

I believe @joeloff already fixed this in a different PR. I'll rerun to force a remerge.

@marcpopMSFT
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@marcpopMSFT
Copy link
Member

Disabled the four tests that were failing in the last run. @dsplaisted it doesn't look like I can make the cppcli tests work in main because the SDK expects one set of apphost/targeting packs from it's stage 0 version but a different verison of the runtime is installed. I could try overwriting the RuntimeFrameworkVersion but that doesn't affect the targeting packs. I could maybe add in an override for the targeting packs as well but it would be more involved as we don't have a simple way of overriding that.

@v-wuzhai v-wuzhai requested a review from marcpopMSFT December 2, 2022 08:21
@dsplaisted
Copy link
Member

@marcpopMSFT Are the projects for those tests using NuGet PackageReference support? I believe that in that case it shouldn't matter whether the installed versions match exactly because it should download what it needs during restore. We've probably never validated that since PackageReference support was added though, so there might be something we need to update to make it work.

@marcpopMSFT
Copy link
Member

@dsplaisted good idea. I'll have to add an extra package reference to the project as the support doesn't work without it but that appears to unblock the tests. I'll do that as a separate PR and I'll also file an issue that cppcli package reference support should enable implicit apphost download without requiring an additional reference.

@marcpopMSFT marcpopMSFT merged commit 3a12a4c into main Dec 2, 2022
@marcpopMSFT marcpopMSFT deleted the v-wuzhai/Merge702tomain branch December 2, 2022 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.