Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aspire: Support Azure Functions Prototype #4252

Closed

Merge remote-tracking branch 'upstream/main' into ellismg/aspire-azur…

56dea13
Select commit
Loading
Failed to load commit list.
Closed

aspire: Support Azure Functions Prototype #4252

Merge remote-tracking branch 'upstream/main' into ellismg/aspire-azur…
56dea13
Select commit
Loading
Failed to load commit list.
Azure Pipelines / azure-dev - cli failed Sep 10, 2024 in 1h 3m 33s

Build #20240910.2 had test failures

Details

Tests

  • Failed: 4 (0.97%)
  • Passed: 399 (96.38%)
  • Other: 11 (2.66%)
  • Total: 414

Annotations

Check failure on line 1875 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure-dev - cli

Build log #L1875

Script failed with exit code: 1

Check failure on line 797 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure-dev - cli

Build log #L797

Script failed with exit code: 1

Check failure on line 1907 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure-dev - cli

Build log #L1907

Script failed with exit code: 1

Check failure on line 1 in Test_CLI_Up_Down_ContainerApp_RemoteBuild

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure-dev - cli

Test_CLI_Up_Down_ContainerApp_RemoteBuild

Failed
Raw output
=== RUN   Test_CLI_Up_Down_ContainerApp_RemoteBuild
=== PAUSE Test_CLI_Up_Down_ContainerApp_RemoteBuild
=== CONT  Test_CLI_Up_Down_ContainerApp_RemoteBuild
    up_test.go:295: DIR: /tmp/Test_CLI_Up_Down_ContainerApp_RemoteBuild4024974995/001
    recording.go:352: recorderProxy started with mode replay at https://127.0.0.1:46047
    up_test.go:300: AZURE_ENV_NAME: azdtest-w1574a7
    cli.go:235: 54ms [stdout] 
    cli.go:235: 56ms [stdout] Initializing an app to run on Azure (azd init)
    cli.go:235: 56ms [stdout] 
    cli.go:235: 61ms [stdout] Enter a new environment name: 
    cli.go:235: 67ms [stdout] SUCCESS: New project initialized!
    cli.go:235: 77ms [stdout] You can view the template code in your directory: /tmp/Test_CLI_Up_Down_ContainerApp_RemoteBuild4024974995/001
    cli.go:235: 86ms [stdout] Learn more about running 3rd party code on our DevHub: https://aka.ms/azd-third-party-code-notice
    cli.go:235: 50ms [stdout] 
    cli.go:235: 52ms [stdout] Provisioning Azure resources (azd provision)
    cli.go:235: 57ms [stdout] Provisioning Azure resources can take some time.
    cli.go:235: 57ms [stdout] 
    cli.go:235: 626ms [stdout] Initialize bicep provider
    cli.go:235: 7.607s [stdout] Reading subscription and location from environment...
    cli.go:235: 7.865s [stdout] Subscription: Azure SDK Developer Playground (faa080af-c1d8-40ad-9cce-e1a450ca5b57)
    cli.go:235: 7.866s [stdout] Location: East US 2
    cli.go:235: 7.866s [stdout] 
    cli.go:235: 7.92s [stdout] Comparing deployment state
    cli.go:235: 7.931s [stdout] Comparing deployment state
    cli.go:235: 7.949s [stdout] Creating/Updating resources
    cli.go:235: 8.013s [stdout] 
    cli.go:235: 8.022s [stdout] SUCCESS: Your application was provisioned in Azure in 7 seconds.
    cli.go:235: 8.038s [stdout] You can view the resources created under the resource group rg-azdtest-w1574a7 in Azure Portal:
    cli.go:235: 8.052s [stdout] https://portal.azure.com/#@/resource/subscriptions/faa080af-c1d8-40ad-9cce-e1a450ca5b57/resourceGroups/rg-azdtest-w1574a7/overview
    cli.go:235: 86ms [stdout] 
    cli.go:235: 88ms [stdout] Deploying services (azd deploy)
    cli.go:235: 88ms [stdout] 
    cli.go:235: 89ms [stdout] Deploying service app
    cli.go:235: 582ms [stdout]   (x) Failed: Deploying service app
    cli.go:235: 584ms [stdout] 
    cli.go:235: 593ms [stdout] ERROR: failed deploying service 'app': remote build only supports the linux/amd64 platform
    up_test.go:317: 
        	Error Trace:	/mnt/vss/_work/1/s/cli/azd/test/functional/up_test.go:317
        	Error:      	Received unexpected error:
        	            	command 'azd deploy --cwd /tmp/Test_CLI_Up_Down_ContainerApp_RemoteBuild4024974995/001/src/app in /tmp/Test_CLI_Up_Down_ContainerApp_RemoteBuild4024974995/001' had non-zero exit code: exit status 1
        	Test:       	Test_CLI_Up_Down_ContainerApp_RemoteBuild
--- FAIL: Test_CLI_Up_Down_ContainerApp_RemoteBuild (8.79s)

Check failure on line 1 in Test_CLI_Aspire_Deploy

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure-dev - cli

Test_CLI_Aspire_Deploy

Failed
Raw output
=== RUN   Test_CLI_Aspire_Deploy
=== PAUSE Test_CLI_Aspire_Deploy
=== CONT  Test_CLI_Aspire_Deploy
    aspire_test.go:247: DIR: /tmp/aspire-deploy2217087783
    aspire_test.go:261: AZURE_ENV_NAME: azdtest-lf39f93
    cli.go:235: 35ms [stdout] 
    cli.go:235: 37ms [stdout] Initializing an app to run on Azure (azd init)
    cli.go:235: 37ms [stdout] 
    cli.go:235: 46ms [stdout] Enter a new environment name: 
    cli.go:235: 48ms [stdout] SUCCESS: New project initialized!
    cli.go:235: 56ms [stdout] You can view the template code in your directory: /tmp/aspire-deploy2217087783
    cli.go:235: 64ms [stdout] Learn more about running 3rd party code on our DevHub: https://aka.ms/azd-third-party-code-notice
    cli.go:235: 633ms [stdout] Analyzing Aspire Application (this might take a moment...)
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 10s
    cli.go:235: 13.683s [stdout] Initialize bicep provider
    cli.go:235: 18.311s [stdout] Select an Azure Subscription to use (or hit enter to use the default  8. Azure SDK Test Resources (2cd617ea-1866-46b1-90e3-fffb087ebf9b)): 
    cli.go:235: 18.313s [stdout] Packaging services (azd package)
    cli.go:235: 18.313s [stdout] 
    cli.go:235: 18.465s [stdout] 
    cli.go:235: 18.475s [stdout] Provisioning Azure resources (azd provision)
    cli.go:235: 18.481s [stdout] Provisioning Azure resources can take some time.
    cli.go:235: 18.482s [stdout] 
    cli.go:235: 18.591s [stdout] Initialize bicep provider
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 20s
    cli.go:235: 24.162s [stdout] Reading subscription and location from environment...
    cli.go:235: 27.055s [stdout] Subscription: Azure SDK Test Resources (2cd617ea-1866-46b1-90e3-fffb087ebf9b)
    cli.go:235: 27.056s [stdout] Location: East US 2
    cli.go:235: 27.056s [stdout] 
    cli.go:235: 27.057s [stdout] Creating a deployment plan
    cli.go:235: 27.068s [stdout] Comparing deployment state
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 30s
    cli.go:235: 38.08s [stdout] Creating/Updating resources
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 40s
    cli.go:235: 41.387s [stdout]   You can view detailed progress in the Azure Portal:
    cli.go:235: 41.408s [stdout]   https://portal.azure.com/#view/HubsExtension/DeploymentDetailsBlade/~/overview/id/%2Fsubscriptions%2F2cd617ea-1866-46b1-90e3-fffb087ebf9b%2Fproviders%2FMicrosoft.Resources%2Fdeployments%2Fazdtest-lf39f93-1725994705
    cli.go:235: 41.408s [stdout] 
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 50s
    cli.go:235: 52.202s [stdout]   (✓) Done: Resource group: rg-azdtest-lf39f93 (1.087s)
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 1m0s
    cli.go:235: 1m2.886s [stdout]   (✓) Done: Container Registry: acrosb5wj353zqys (9.245s)
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 1m10s
    cli.go:235: 1m13.453s [stdout]   (✓) Done: Log Analytics workspace: law-osb5wj353zqys (19.411s)
    cli.go:235: 1m13.454s [stdout]   (✓) Done: Key Vault: kvf2edecb5osb5wj353zqys (19.981s)
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 1m20s
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 1m30s
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 1m40s
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 1m50s
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 2m0s
    cli.go:210: [heartbeat] command azd up in /tmp/aspire-deploy2217087783 is still running after 2m10s
    cli.go:210: [heartbeat] 

Check failure on line 1 in Test_CLI_Up_Down_ContainerApp_RemoteBuild

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure-dev - cli

Test_CLI_Up_Down_ContainerApp_RemoteBuild

Failed
Raw output
=== RUN   Test_CLI_Up_Down_ContainerApp_RemoteBuild
=== PAUSE Test_CLI_Up_Down_ContainerApp_RemoteBuild
=== CONT  Test_CLI_Up_Down_ContainerApp_RemoteBuild
    up_test.go:295: DIR: C:\Users\CLOUDT~1\AppData\Local\Temp\Test_CLI_Up_Down_ContainerApp_RemoteBuild1110803286\001
    recording.go:352: recorderProxy started with mode replay at https://127.0.0.1:55449
    up_test.go:300: AZURE_ENV_NAME: azdtest-w1574a7
    cli.go:235: 236ms [stdout] 
    cli.go:235: 241ms [stdout] Initializing an app to run on Azure (azd init)
    cli.go:235: 241ms [stdout] 
    cli.go:235: 294ms [stdout] Enter a new environment name: 
    cli.go:235: 294ms [stdout] SUCCESS: New project initialized!
    cli.go:235: 306ms [stdout] You can view the template code in your directory: C:\Users\CLOUDT~1\AppData\Local\Temp\Test_CLI_Up_Down_ContainerApp_RemoteBuild1110803286\001
    cli.go:235: 334ms [stdout] Learn more about running 3rd party code on our DevHub: https://aka.ms/azd-third-party-code-notice
    cli.go:235: 164ms [stdout] 
    cli.go:235: 166ms [stdout] Provisioning Azure resources (azd provision)
    cli.go:235: 169ms [stdout] Provisioning Azure resources can take some time.
    cli.go:235: 169ms [stdout] 
    cli.go:235: 681ms [stdout] Initialize bicep provider
    cli.go:235: 6.451s [stdout] Reading subscription and location from environment...
    cli.go:235: 6.846s [stdout] Subscription: Azure SDK Developer Playground (faa080af-c1d8-40ad-9cce-e1a450ca5b57)
    cli.go:235: 6.85s [stdout] Location: East US 2
    cli.go:235: 6.85s [stdout] 
    cli.go:235: 6.925s [stdout] Comparing deployment state
    cli.go:235: 6.929s [stdout] Comparing deployment state
    cli.go:235: 6.966s [stdout] Creating/Updating resources
    cli.go:235: 7.109s [stdout] 
    cli.go:235: 7.117s [stdout] SUCCESS: Your application was provisioned in Azure in 6 seconds.
    cli.go:235: 7.18s [stdout] You can view the resources created under the resource group rg-azdtest-w1574a7 in Azure Portal:
    cli.go:235: 7.186s [stdout] https://portal.azure.com/#@/resource/subscriptions/faa080af-c1d8-40ad-9cce-e1a450ca5b57/resourceGroups/rg-azdtest-w1574a7/overview
    recording.go:524: {"time":"2024-09-10T19:04:24.2813891Z","level":"ERROR","msg":"connectHandler failed to read HTTP request","error":"read tcp 127.0.0.1:55449->127.0.0.1:55484: wsarecv: An existing connection was forcibly closed by the remote host."}
    recording.go:524: {"time":"2024-09-10T19:04:24.2813891Z","level":"ERROR","msg":"connectHandler failed to read HTTP request","error":"read tcp 127.0.0.1:55449->127.0.0.1:55466: wsarecv: An existing connection was forcibly closed by the remote host."}
    cli.go:235: 296ms [stdout] 
    cli.go:235: 296ms [stdout] Deploying services (azd deploy)
    cli.go:235: 296ms [stdout] 
    cli.go:235: 300ms [stdout] Deploying service app
    cli.go:235: 1.162s [stdout]   (x) Failed: Deploying service app
    cli.go:235: 1.162s [stdout] 
    cli.go:235: 1.167s [stdout] ERROR: failed deploying service 'app': remote build only supports the linux/amd64 platform
    recording.go:524: {"time":"2024-09-10T19:04:25.517871Z","level":"ERROR","msg":"connectHandler failed to read HTTP request","error":"read tcp 127.0.0.1:55449->127.0.0.1:55504: wsarecv: An existing connection was forcibly closed by the remote host."}
    up_test.go:317: 
        	Error Trace:	D:/a/_work/1/s/cli/azd/test/functional/up_test.go:317
        	Error:      	Received unexpected error:
        	            	command 'azd deploy --cwd C:\Users\CLOUDT~1\AppData\Local\Temp\Test_CLI_Up_Down_ContainerApp_RemoteBuild1110803286\001\src\app in C:\Users\CLOUDT~1\AppData\Local\Temp\Test_CLI_Up_Down_ContainerApp_RemoteBuild1110803286\001' had non-zero exit code: exit status 1
        	Test:       	Test_CLI_Up_Down_ContainerApp_RemoteBuild
--- FAIL: Test_CLI_Up_Down_ContainerApp_RemoteBuild (8.85s)

Check failure on line 1 in Test_CLI_Up_Down_ContainerApp_RemoteBuild

See this annotation in the file changed.

@azure-pipelines azure-pipelines / azure-dev - cli

Test_CLI_Up_Down_ContainerApp_RemoteBuild

Failed
Raw output
=== RUN   Test_CLI_Up_Down_ContainerApp_RemoteBuild
=== PAUSE Test_CLI_Up_Down_ContainerApp_RemoteBuild
=== CONT  Test_CLI_Up_Down_ContainerApp_RemoteBuild
    up_test.go:295: DIR: /var/folders/q8/68hhzv8d7tq6gcjbsy0347_r0000gn/T/Test_CLI_Up_Down_ContainerApp_RemoteBuild630659132/001
    recording.go:352: recorderProxy started with mode replay at https://127.0.0.1:50103
    up_test.go:300: AZURE_ENV_NAME: azdtest-w1574a7
    cli.go:235: 41ms [stdout] 
    cli.go:235: 43ms [stdout] Initializing an app to run on Azure (azd init)
    cli.go:235: 43ms [stdout] 
    cli.go:235: 92ms [stdout] Enter a new environment name: 
    cli.go:235: 95ms [stdout] SUCCESS: New project initialized!
    cli.go:235: 104ms [stdout] You can view the template code in your directory: /private/var/folders/q8/68hhzv8d7tq6gcjbsy0347_r0000gn/T/Test_CLI_Up_Down_ContainerApp_RemoteBuild630659132/001
    cli.go:235: 112ms [stdout] Learn more about running 3rd party code on our DevHub: https://aka.ms/azd-third-party-code-notice
    cli.go:235: 39ms [stdout] 
    cli.go:235: 41ms [stdout] Provisioning Azure resources (azd provision)
    cli.go:235: 42ms [stdout] Provisioning Azure resources can take some time.
    cli.go:235: 42ms [stdout] 
    cli.go:235: 398ms [stdout] Initialize bicep provider
    cli.go:235: 3.984s [stdout] Reading subscription and location from environment...
    cli.go:235: 4.197s [stdout] Subscription: Azure SDK Developer Playground (faa080af-c1d8-40ad-9cce-e1a450ca5b57)
    cli.go:235: 4.198s [stdout] Location: East US 2
    cli.go:235: 4.198s [stdout] 
    cli.go:235: 4.216s [stdout] Creating a deployment plan
    cli.go:235: 4.217s [stdout] Comparing deployment state
    cli.go:235: 4.23s [stdout] Creating/Updating resources
    cli.go:235: 4.256s [stdout] 
    cli.go:235: 4.258s [stdout] SUCCESS: Your application was provisioned in Azure in 4 seconds.
    cli.go:235: 4.263s [stdout] You can view the resources created under the resource group rg-azdtest-w1574a7 in Azure Portal:
    cli.go:235: 4.266s [stdout] https://portal.azure.com/#@/resource/subscriptions/faa080af-c1d8-40ad-9cce-e1a450ca5b57/resourceGroups/rg-azdtest-w1574a7/overview
    cli.go:235: 39ms [stdout] 
    cli.go:235: 40ms [stdout] Deploying services (azd deploy)
    cli.go:235: 40ms [stdout] 
    cli.go:235: 41ms [stdout] Deploying service app
    cli.go:235: 612ms [stdout]   (x) Failed: Deploying service app
    cli.go:235: 612ms [stdout] 
    cli.go:235: 617ms [stdout] ERROR: failed deploying service 'app': remote build only supports the linux/amd64 platform
    up_test.go:317: 
        	Error Trace:	/Users/runner/work/1/s/cli/azd/test/functional/up_test.go:317
        	Error:      	Received unexpected error:
        	            	command 'azd deploy --cwd /var/folders/q8/68hhzv8d7tq6gcjbsy0347_r0000gn/T/Test_CLI_Up_Down_ContainerApp_RemoteBuild630659132/001/src/app in /var/folders/q8/68hhzv8d7tq6gcjbsy0347_r0000gn/T/Test_CLI_Up_Down_ContainerApp_RemoteBuild630659132/001' had non-zero exit code: exit status 1
        	Test:       	Test_CLI_Up_Down_ContainerApp_RemoteBuild
--- FAIL: Test_CLI_Up_Down_ContainerApp_RemoteBuild (5.03s)