- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for jest (0.17 sec)
-
ci/official/bisect.sh
# # Note that you can combine bisect.sh with any.sh to bisect a single test: # # export TFCI=... # export TF_BISECT_SCRIPT=ci/official/any.sh # export TF_BISECT_GOOD=a_good_commit_sha # export TF_BISECT_BAD=a_failing_commit_sha # export TF_ANY_TARGETS="quoted list of targets, like on the command line" # export TF_ANY_MODE=test set -euxo pipefail cd "$(dirname "$0")/../../" # tensorflow/
Shell Script - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 1.8K bytes - Viewed (0) -
ci/official/utilities/setup_macos.sh
exit 1 fi # "TFCI_MACOS_BAZEL_TEST_DIR_PATH" specifies the directory that Bazel should use # when running tests. Each test will be executed in a separate subdirectory # inside this directory. TF Mac builds need ~150 GB of disk space to be able to # run all the tests. Since TFCI Mac VMs execute Bazel test commands in a # partition with insufficient storage, we specify the # 'TFCI_MACOS_BAZEL_TEST_DIR_PATH' environment variable to point to a partition
Shell Script - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Feb 15 15:23:28 GMT 2024 - 6.2K bytes - Viewed (0) -
ci/official/utilities/rename_and_verify_wheels.sh
fi # VERY basic check to ensure the [and-cuda] package variant is installable. # Checks TFCI_BAZEL_COMMON_ARGS for "gpu" or "cuda", implying that the test is # relevant. All of the GPU test machines have CUDA installed via other means, # so I am not sure how to verify that the dependencies themselves are valid for # the moment. if [[ "$TFCI_BAZEL_COMMON_ARGS" =~ gpu|cuda ]]; then echo "Checking to make sure tensorflow[and-cuda] is installable..."
Shell Script - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Mar 27 21:16:27 GMT 2024 - 3.4K bytes - Viewed (0) -
ci/official/utilities/setup.sh
# # Common setup for all TF scripts. # # Make as FEW changes to this file as possible. It should not contain utility # functions (except for tfrun); use dedicated scripts instead and reference them # specifically. Use your best judgment to keep the scripts in this directory # lean and easy to follow. When in doubt, remember that for CI scripts, "keep it # simple" is MUCH more important than "don't repeat yourself."
Shell Script - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Fri Jan 26 00:33:34 GMT 2024 - 5.2K bytes - Viewed (1) -
ci/official/any.sh
# any.sh has two run modes. # # 1. RUN, TEST, OR BUILD BAZEL TARGET(S) WITHIN A TFCI ENVIRONMENT # To use: # export TFCI=ci/official/envs/env_goes_here # export TF_ANY_TARGETS="quoted list of targets, like on the command line" # export TF_ANY_MODE="test" or "build" or "run" (default: "test") # ./any.sh # # 2. RUN ANY OTHER SCRIPT AND ENV WITH NO SIDE EFFECTS (NO UPLOADS)
Shell Script - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 2.1K bytes - Viewed (1) -
ci/official/upload.sh
# $TF_VER_FULL will resolve to e.g. "2.15.0-rc2". Since $TF_VER_FULL comes # from get_versions.sh, which must be run *after* update_version.py, FINAL_URI # can't be set inside the rest of the _upload envs. FINAL_URI="$TFCI_ARTIFACT_FINAL_GCS_URI/$TF_VER_FULL" gsutil -m rsync -d -r "$DOWNLOADS" "$FINAL_URI" # Also mirror the latest-uploaded folder to the "latest" directory.
Shell Script - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Jan 24 20:52:12 GMT 2024 - 2.8K bytes - Viewed (0)