presets: remove eternal test_timeout_filtering (#758)
In practice we've disabled this setting at some clients, because there's not a surrounding workflow to find these targets are being silently dropped from CI, nor run them on another schedule. We can re-introduce something better when we add Test Selection to Aspect Workflows.
This commit is contained in:
parent
8c95f4aef6
commit
251b1d07db
|
@ -1,10 +1,3 @@
|
|||
# We recommend enforcing a policy that keeps your CI from being slowed down
|
||||
# by individual test targets that should be optimized
|
||||
# or split up into multiple test targets with sharding or manually.
|
||||
# Set this flag to exclude targets that have their timeout set to eternal (>15m) from running on CI.
|
||||
# Docs: https://bazel.build/docs/user-manual#test-timeout-filters
|
||||
test --test_timeout_filters=-eternal
|
||||
|
||||
# Set this flag to enable re-tries of failed tests on CI.
|
||||
# When any test target fails, try one or more times. This applies regardless of whether the "flaky"
|
||||
# tag appears on the target definition.
|
||||
|
|
|
@ -1,10 +1,3 @@
|
|||
# We recommend enforcing a policy that keeps your CI from being slowed down
|
||||
# by individual test targets that should be optimized
|
||||
# or split up into multiple test targets with sharding or manually.
|
||||
# Set this flag to exclude targets that have their timeout set to eternal (>15m) from running on CI.
|
||||
# Docs: https://bazel.build/docs/user-manual#test-timeout-filters
|
||||
test --test_timeout_filters=-eternal
|
||||
|
||||
# Set this flag to enable re-tries of failed tests on CI.
|
||||
# When any test target fails, try one or more times. This applies regardless of whether the "flaky"
|
||||
# tag appears on the target definition.
|
||||
|
|
Loading…
Reference in New Issue