Skip to content

Update props and nuspec

ed4febb
Select commit
Loading
Failed to load commit list.
Merged

Remove GenerateRuntimeConfigDevFile & update nuspec paths #4507

Update props and nuspec
ed4febb
Select commit
Loading
Failed to load commit list.
Azure Pipelines / coretools.public succeeded Jul 8, 2025 in 28m 0s

Build #4.0.10000-pr.25358.0 had test failures

Details

Tests

  • Failed: 2 (0.57%)
  • Passed: 348 (99.43%)
  • Other: 0 (0.00%)
  • Total: 350

Annotations

Check failure on line 1 in Azure.Functions.Cli.E2E.Tests.Commands.FuncInit.DotnetInitTests.Init_WithSupportedTargetFramework_GeneratesProjectFile_ContainsExpectedVersion(targetFramework: "net6.0")

See this annotation in the file changed.

@azure-pipelines azure-pipelines / coretools.public

Azure.Functions.Cli.E2E.Tests.Commands.FuncInit.DotnetInitTests.Init_WithSupportedTargetFramework_GeneratesProjectFile_ContainsExpectedVersion(targetFramework: "net6.0")

Expected command to exit with 0 but it did not. Error message: No templates or subcommands found matching: 'func'.
Did you mean one of the following templates?
   dotnet new sln
   dotnet new nunit
   dotnet new xunit
   dotnet new mvc
   dotnet new grpc

To list installed templates similar to 'func', run:
   dotnet new list func
To search for the templates on NuGet.org, run:
   dotnet new search func


For details on the exit code, refer to https://aka.ms/templating-exit-codes#103

Error creating project template
Raw output
   at FluentAssertions.Execution.XUnit2TestFramework.Throw(String message)
   at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionScope.FailWith(String message, Object[] args)
   at Azure.Functions.Cli.TestFramework.Assertions.CommandResultAssertions.ExitWith(Int32 expectedExitCode) in /_/test/Cli/TestFramework/Assertions/CommandResultAssertions.cs:line 18
   at Azure.Functions.Cli.E2E.Tests.Commands.FuncInit.DotnetInitTests.Init_WithSupportedTargetFramework_GeneratesProjectFile_ContainsExpectedVersion(String targetFramework) in /_/test/Cli/Func.E2E.Tests/Commands/FuncInit/DotnetInitTests.cs:line 63
   at InvokeStub_DotnetInitTests.Init_WithSupportedTargetFramework_GeneratesProjectFile_ContainsExpectedVersion(Object, Span`1)
   at System.Reflection.MethodBaseInvoker.InvokeWithOneArg(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

Check failure on line 1 in Azure.Functions.Cli.E2E.Tests.Commands.FuncStart.LogLevelTests.Start_LanguageWorker_LogLevelOverridenViaHostJson_LogLevelSetToExpectedValue

See this annotation in the file changed.

@azure-pipelines azure-pipelines / coretools.public

Azure.Functions.Cli.E2E.Tests.Commands.FuncStart.LogLevelTests.Start_LanguageWorker_LogLevelOverridenViaHostJson_LogLevelSetToExpectedValue

The command output did not contain expected result: Worker process started and initialized
Raw output
   at FluentAssertions.Execution.XUnit2TestFramework.Throw(String message)
   at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionScope.FailWith(String message, Object[] args)
   at Azure.Functions.Cli.TestFramework.Assertions.CommandResultAssertions.HaveStdOutContaining(String pattern) in /_/test/Cli/TestFramework/Assertions/CommandResultAssertions.cs:line 25
   at Azure.Functions.Cli.E2E.Tests.Commands.FuncStart.LogLevelTests.Start_LanguageWorker_LogLevelOverridenViaHostJson_LogLevelSetToExpectedValue() in /_/test/Cli/Func.E2E.Tests/Commands/FuncStart/LogLevelTests.cs:line 95
--- End of stack trace from previous location ---