aspnetcore icon indicating copy to clipboard operation
aspnetcore copied to clipboard

Quarantining `BlazorWasmHostedTemplate_AzureActiveDirectoryTemplate_Works`

Open sebastienros opened this issue 3 years ago • 4 comments

Failing Test(s)

  • BlazorWasmHostedTemplate_AzureActiveDirectoryTemplate_Works in src/ProjectTemplates/BlazorTemplates.Tests/BlazorTemplateTest.cs

Error Message

error : The file '/tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq/Client/obj/project.nuget.cache' already exists.

Stacktrace

Failed BlazorTemplates.Tests.BlazorWasmTemplateTest.BlazorWasmHostedTemplate_AzureActiveDirectoryTemplate_Works(instance: TemplateInstance { Arguments = ["-ho", "-au", "SingleOrg", "--calls-graph", "--domain", ...], Name = "blazorwasmhostedaadgraph" }) [2 s]
  Error Message:
   Project new blazorwasm  -ho -au SingleOrg --calls-graph --domain my-domain --tenant-id tenantId --client-id clientId --default-scope full --app-id-uri ApiUri --api-client-id 1234123413241324 failed to create/restore. Exit code -1.
/private/tmp/helix/working/A97408FB/p/dotnet-cli/dotnet new blazorwasm  --debug:disable-sdk-templates --debug:custom-hive "/private/tmp/helix/working/A97408FB/w/9C9608B1/e/Hives/.templateEngine" -ho -au SingleOrg --calls-graph --domain my-domain --tenant-id tenantId --client-id clientId --default-scope full --app-id-uri ApiUri --api-client-id 1234123413241324 -o /tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq\nStdErr: Restore failed.
Post action failed.
Manual instructions: Run 'dotnet restore'
\nStdOut: The template "Blazor WebAssembly App" was created successfully.
This template contains technologies from parties other than Microsoft, see https://aka.ms/aspnetcore/6.0-third-party-notices for details.

Processing post-creation actions...
Running 'dotnet restore' on /tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq/AspNet.jjso4iuzrzq.sln...
  Determining projects to restore...
  Restored /private/tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq/Shared/AspNet.jjso4iuzrzq.Shared.csproj (in 122 ms).
  Restored /tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq/Shared/AspNet.jjso4iuzrzq.Shared.csproj (in 122 ms).
  Restored /private/tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq/Client/AspNet.jjso4iuzrzq.Client.csproj (in 310 ms).
/private/tmp/helix/working/A97408FB/p/dotnet-cli/sdk/7.0.100-alpha.1.21518.14/NuGet.targets(130,5): error : The file '/tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq/Client/obj/project.nuget.cache' already exists. [/tmp/helix/working/A97408FB/w/9C9608B1/e/Templates/BaseFolder/AspNet.jjso4iuzrzq/AspNet.jjso4iuzrzq.sln]


Expected: True
Actual:   False
  Stack Trace:
     at BlazorTemplates.Tests.BlazorTemplateTest.CreateBuildPublishAsync(String projectName, String auth, String[] args, String targetFramework, Boolean serverProject, Boolean onlyCreate) in /_/src/ProjectTemplates/BlazorTemplates.Tests/BlazorTemplateTest.cs:line 39

Logs


Build

https://dev.azure.com/dnceng/public/_build/results?buildId=1436533&view=logs&j=3f6d4e0f-1b71-56b5-361e-d95b6e6da15a&t=d5bf30bc-9e5a-596c-d1c8-39e2dfa42d49

sebastienros avatar Oct 22 '21 23:10 sebastienros

This is a Playright test & duplicate of a E2E test we already have as @sebastienros pointed out in the PR: https://github.com/dotnet/aspnetcore/pull/37783#issuecomment-950177799.

As such, I don't believe we'll need/want to tackle this in 6.0 docs & infra. cc/ @HaoK any objections?

TanayParikh avatar Oct 26 '21 23:10 TanayParikh

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

ghost avatar Oct 28 '21 21:10 ghost

Tests currently skipped via https://github.com/dotnet/aspnetcore/pull/40129, will be unskipped via https://github.com/dotnet/aspnetcore/issues/38818 along with being re-enabled in helix.

TanayParikh avatar Feb 10 '22 20:02 TanayParikh

Tried out this test locally. It just times out. The original project.nuget.cache issue doesn't seem specific to this test, and could be attributed to momentary flakiness.

TanayParikh avatar Dec 22 '22 00:12 TanayParikh

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost avatar Mar 01 '23 17:03 ghost

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost avatar Oct 06 '23 17:10 ghost

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost avatar Dec 14 '23 18:12 ghost