search

Azure / azure-dev

A developer CLI that reduces the time it takes for you to get started on Azure. The Azure Developer CLI (azd) provides a set of developer-friendly commands that map to key stages in your workflow - code, build, deploy, monitor, repeat.
https://aka.ms/azd
MIT License
412 stars 201 forks source link

[codespaces] sizing issue - requires higher configuration #970

Closed v-jiaodi closed 2 years ago

v-jiaodi commented 2 years ago

Describe the issue: Individual deploy test error

Repro Steps: 1.Run command: bash ./test-templates.sh -c false -t <template_name> -b pr/551. 2.Change “complete” to “completed” in UI 3.Run azd deploy --service web

Error Message:

image

Environment: OS: Codespace. Templates: https://github.com/Azure-Samples/todo-csharp-sql-swa-func https://github.com/Azure-Samples/todo-python-mongo-swa-func Branch: pr/551

Expected behavior: Run azd deploy --service web can run successfully.

@jongio for notification.

rajeshkamal5050 commented 2 years ago

cc: @danieljurek for Codespace environment

jongio commented 2 years ago

Yes, I ran into this too. You need to use a bigger codespace spec. You can go to https://github.com/codespaces/ and change it.

danieljurek commented 2 years ago

This reads exactly like an out of memory error that we encountered previously. Moving up to an 8GB VM should get you past this problem. We have a PR to move the machine size up by default.

zedy-wj commented 2 years ago

@jongio, @danieljurek - We have changed the machine size to 4 core 8GB, but it failed when we executed bash ./test-templates.sh -c false -t Azure-Samples/todo-csharp-sql-swa-func this time. The error message was shown as below: image

rajeshkamal5050 commented 2 years ago

@weikanglim do you see this issue when running this template in Codespaces?

weikanglim commented 2 years ago

@zedy-wj That was caused by a separate issue that's now been fixed. Can you verify if everything is working as expected, and close if necessary?

zedy-wj commented 2 years ago

@weikanglim - We have verified with 4 core 8GB and this issue is no longer reproduced. Besides, the smallest size we can create now is 4 core 8GB. We will close it, thanks.