|
1 | 1 | # CIRRUS CONFIGURATION FILE
|
2 | 2 | # https://cirrus-ci.org/guide/writing-tasks/
|
3 | 3 |
|
| 4 | +# YAML anchors used to share fields between tasks. |
| 5 | +# See https://confluence.atlassian.com/bitbucket/yaml-anchors-960154027.html |
4 | 6 | web_shard_template: &WEB_SHARD_TEMPLATE
|
5 | 7 | only_if: "changesInclude('.cirrus.yml', 'dev/**', 'packages/flutter/**', 'packages/flutter_test/**', 'packages/flutter_tools/lib/src/test/**', 'packages/flutter_web_plugins/**', 'bin/internal/**') || $CIRRUS_PR == ''"
|
6 | 8 | environment:
|
@@ -32,6 +34,18 @@ macos_shard_template: &MACOS_SHARD_TEMPLATE
|
32 | 34 | - ulimit -S -n 2048 # https://github.com/flutter/flutter/issues/2976
|
33 | 35 | - dart --enable-asserts ./dev/bots/test.dart
|
34 | 36 |
|
| 37 | +firebase_shard_template: &FIREBASE_SHARD_TEMPLATE |
| 38 | + environment: |
| 39 | + # Empirically, this shard runs in 20-25 minutes with just one CPU and 4G of RAM, as of |
| 40 | + # October 2019. It does not seem to be sensitive to the number of CPUs or amount of RAM; |
| 41 | + # doubling CPUs had no effect (mere seconds under 20 minutes), increasing RAM to 24G left it |
| 42 | + # on the high end of the 20-25 minute range. (This makes sense, as it's just driving the |
| 43 | + # Firebase test lab remotely.) Less than 4G of RAM made it go OOM. |
| 44 | + CLOUDSDK_CORE_DISABLE_PROMPTS: 1 |
| 45 | + GCLOUD_FIREBASE_TESTLAB_KEY: ENCRYPTED[1c140257edc48f5578fa5a0e5038b84c8e53270c405efa5a8e35ea303a4e0d135853989f448f72136206de854d17fbec] |
| 46 | + script: |
| 47 | + - dart --enable-asserts ./dev/bots/test.dart |
| 48 | + |
35 | 49 | use_compute_credits: $CIRRUS_USER_COLLABORATOR == 'true'
|
36 | 50 |
|
37 | 51 | environment:
|
@@ -268,17 +282,15 @@ task:
|
268 | 282 | - git clone https://github.com/flutter/tests.git bin/cache/pkg/tests
|
269 | 283 | - dart --enable-asserts dev/customer_testing/run_tests.dart --skip-on-fetch-failure --skip-template bin/cache/pkg/tests/registry/*.test
|
270 | 284 |
|
271 |
| - - name: firebase_test_lab_tests-linux # linux-only |
272 |
| - environment: |
273 |
| - # Empirically, this shard runs in 20-25 minutes with just one CPU and 4G of RAM, as of |
274 |
| - # October 2019. It does not seem to be sensitive to the number of CPUs or amount of RAM; |
275 |
| - # doubling CPUs had no effect (mere seconds under 20 minutes), increasing RAM to 24G left it |
276 |
| - # on the high end of the 20-25 minute range. (This makes sense, as it's just driving the |
277 |
| - # Firebase test lab remotely.) Less than 4G of RAM made it go OOM. |
278 |
| - CLOUDSDK_CORE_DISABLE_PROMPTS: 1 |
279 |
| - GCLOUD_FIREBASE_TESTLAB_KEY: ENCRYPTED[1c140257edc48f5578fa5a0e5038b84c8e53270c405efa5a8e35ea303a4e0d135853989f448f72136206de854d17fbec] |
280 |
| - script: |
281 |
| - - ./dev/bots/firebase_testlab.sh |
| 285 | + # firebase_test_lab_tests are linux-only |
| 286 | + - name: firebase_test_lab_tests-0-linux |
| 287 | + <<: *FIREBASE_SHARD_TEMPLATE |
| 288 | + |
| 289 | + - name: firebase_test_lab_tests-1-linux |
| 290 | + <<: *FIREBASE_SHARD_TEMPLATE |
| 291 | + |
| 292 | + - name: firebase_test_lab_tests-2-linux |
| 293 | + <<: *FIREBASE_SHARD_TEMPLATE |
282 | 294 |
|
283 | 295 | - name: web_smoke_test
|
284 | 296 | only_if: "changesInclude('.cirrus.yml', 'examples/hello_world/**' ,'dev/**', 'packages/flutter/**', 'packages/flutter_test/**', 'packages/flutter_tools/lib/src/test/**', 'packages/flutter_web_plugins/**', 'bin/internal/**') || $CIRRUS_PR == ''"
|
|
0 commit comments