Commit 7fcf0306 authored by Fedor Korotkov's avatar Fedor Korotkov Committed by Todd Volkert

[ci] more resources to Windows tasks (#45392)

There was a bug in Cirrus that Cirrus always used 4CPU config for Windows Containers even though everything was billed according to the resources configured (in your case 2 CPUs).
parent 4c64b715
...@@ -329,8 +329,8 @@ task: ...@@ -329,8 +329,8 @@ task:
environment: environment:
# It's not clear that changing the cpu/memory fields here has any impact, so we use # It's not clear that changing the cpu/memory fields here has any impact, so we use
# small numbers... # small numbers...
CPU: 2 # 1-8 without compute credits, 1-30 with CPU: 4 # 1-8 without compute credits, 1-30 with
MEMORY: 2G # 256M-24G without compute credits, 256M-90G with MEMORY: 12G # 256M-24G without compute credits, 256M-90G with
CIRRUS_WORKING_DIR: "C:\\Windows\\Temp\\$FLUTTER_SDK_PATH_WITH_SPACE" CIRRUS_WORKING_DIR: "C:\\Windows\\Temp\\$FLUTTER_SDK_PATH_WITH_SPACE"
PATH: "$CIRRUS_WORKING_DIR/bin;$CIRRUS_WORKING_DIR/bin/cache/dart-sdk/bin;$PATH" PATH: "$CIRRUS_WORKING_DIR/bin;$CIRRUS_WORKING_DIR/bin/cache/dart-sdk/bin;$PATH"
pub_cache: pub_cache:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment