build: add new integration tests & bazel-in-bazel tests to … glob (#33927)

Move bazel-in-bazel them to test job & increase it is 2xlarge+. test_integration_bazel is removed. Overall CI credit usage is reduced.

test: include ng_elements_schematics in legacy integration tests temporarily

This test was recently added and use a new pattern that doesn't work with npm_integration_test out of the box. It needs some refactoring to work. Left a TODO for this

PR Close #33927
This commit is contained in:
Greg Magolan
2020-02-14 17:23:49 -08:00
committed by Miško Hevery
parent 983e487a8f
commit 40ae89e3bf
5 changed files with 49 additions and 191 deletions

View File

@ -298,7 +298,7 @@ jobs:
# as they require network access for yarn install), this test is running out of memory
# consistently with the xlarge machine.
# TODO: switch back to xlarge once integration tests are running on remote-exec
resource_class: 2xlarge
resource_class: 2xlarge+
steps:
- custom_attach_workspace
- init_environment
@ -308,21 +308,6 @@ jobs:
command: yarn bazel test //... --build_tag_filters=-ivy-only --test_tag_filters=-ivy-only
no_output_timeout: 20m
test_integration_bazel:
executor:
# Needed because the //integration:bazel-schematics_test test expect Chrome to be installed
name: browsers-executor
resource_class: xlarge
steps:
- custom_attach_workspace
- init_environment
- run:
# Run "exclusive" and "manual" bazel-in-bazel integration tests in their own CI job
# as they take 8m+ to execute and with bazel running inside bazel they are too
# memory intensive to be run in parallel with other tests so are tagged as "exclusive"
command: yarn bazel test //integration:bazel_test //integration:bazel-schematics_test
no_output_timeout: 20m
# Temporary job to test what will happen when we flip the Ivy flag to true
test_ivy_aot:
executor:
@ -842,9 +827,6 @@ workflows:
- test:
requires:
- setup
- test_integration_bazel:
requires:
- setup
- test_ivy_aot:
requires:
- setup