From cec5cd6eb5eceb499c56ee5fb0febe0e887ebce5 Mon Sep 17 00:00:00 2001 From: Paul Gschwendtner Date: Wed, 14 Jun 2023 15:28:45 +0000 Subject: [PATCH] test: mark ngtsc test target as flaky (#50718) A larger investigation on why this is flaky is needed. Currently the test is flaky with around 77% sucess rate and negatively impacts team productivity. Subjectively, as reported by team members this it's much more flaky than a success rate of 77%. PR Close #50718 --- packages/compiler-cli/test/ngtsc/BUILD.bazel | 3 +++ 1 file changed, 3 insertions(+) diff --git a/packages/compiler-cli/test/ngtsc/BUILD.bazel b/packages/compiler-cli/test/ngtsc/BUILD.bazel index 303973283c2..e73677971d5 100644 --- a/packages/compiler-cli/test/ngtsc/BUILD.bazel +++ b/packages/compiler-cli/test/ngtsc/BUILD.bazel @@ -32,6 +32,9 @@ jasmine_node_test( "//packages/compiler-cli/src/ngtsc/testing/fake_common:npm_package", "//packages/compiler-cli/src/ngtsc/testing/fake_core:npm_package", ], + # TODO: This target is flaky on Windows due to the global FS sometimes not being set/reset. + # See: https://app.circleci.com/pipelines/github/angular/angular/62261/workflows/6a4e952c-3d0b-44ab-b3db-c0a639af6bdc/jobs/1348755. + flaky = True, shard_count = 4, deps = [ ":ngtsc_lib",