- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for TFCI (0.02 sec)
-
ci/official/utilities/setup.sh
# TFCI env has been loaded. This is useful for e.g. on-demand "generic" jobs # where the user may wish to change just one option. if [[ -z "${TFCI:-}" ]]; then echo '==TFCI==: The $TFCI variable is not set. This is fine as long as you' echo 'already sourced a TFCI env file with "set -a; source <path>; set +a".' echo 'If you have not, you will see a lot of undefined variable errors.' else
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Aug 07 23:01:25 UTC 2024 - 6K bytes - Viewed (0) -
ci/official/envs/rbe
# check This script checks for such errors early if ! grep "rbe_$TFCI_BAZEL_TARGET_SELECTING_CONFIG_PREFIX" .bazelrc; then cat <<EOF ERROR: RBE was enabled via the 'rbe' env in the 'TFCI' variable. TFCI: $TFCI TFCI_BAZEL_TARGET_SELECTING_CONFIG_PREFIX is "$TFCI_BAZEL_TARGET_SELECTING_CONFIG_PREFIX". But in .bazelrc, there is no "rbe_$TFCI_BAZEL_TARGET_SELECTING_CONFIG_PREFIX".
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Fri Aug 09 16:05:18 UTC 2024 - 2.7K bytes - Viewed (0) -
ci/official/envs/ci_default
# ============================================================================== # Note: this file gets sourced in utilities/setup.sh, which has "set -u" # (error on undefined variables). This ensures that (a) every TFCI variable # has an explicit default value, and (b) no script can accidentally use a # variable that doesn't exist. Please keep this list in alphabetical order. # # Find usage in scripts with e.g.: # cd ci/official
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Sep 18 20:47:34 UTC 2024 - 2.7K bytes - Viewed (0)