- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 11 for Testing (0.3 sec)
-
ci/official/wheel_test/README.md
## Wheel Test This directory is dedicated to tests that require a built TensorFlow wheel file for testing, such as: * Ensuring the entire API is importable * Testing downstream projects against the wheel Ensure you have Bazel installed and accessible from your command line. These tests use hermetic Python. They also require a built TensorFlow wheel file and a requirements_lock file. The requirements_lock file is generated by the
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Aug 31 18:17:57 GMT 2023 - 3.3K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/aarch64.bazelrc
build:sigbuild_remote_cache --remote_cache="https://storage.googleapis.com/tensorflow-devinfra-bazel-cache/manylinux2014" --remote_upload_local_results=false # Change the value of CACHEBUSTER when upgrading the toolchain, or when testing # different compilation methods. E.g. for a PR to test a new CUDA version, set # the CACHEBUSTER to the PR number. build --action_env=CACHEBUSTER=20220325 # Use Python 3.X as installed in container image
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Tue Nov 21 12:25:39 GMT 2023 - 5.8K bytes - Viewed (0) -
ci/official/README.md
1. Creating a PR and observing the presubmit test results 2. Running the CI scripts locally, as explained below 3. **Google employees only**: Google employees can use an internal-only tool called "MLCI" that makes testing more convenient: it can execute any full CI job against a pending change. Search for "MLCI" internally to find it. You may invoke a CI script of your choice by following these instructions: ```bash cd tensorflow-git-dir
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 8K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/aarch64_clang.bazelrc
build:sigbuild_remote_cache --remote_cache="https://storage.googleapis.com/tensorflow-devinfra-bazel-cache/manylinux2014" --remote_upload_local_results=false # Change the value of CACHEBUSTER when upgrading the toolchain, or when testing # different compilation methods. E.g. for a PR to test a new CUDA version, set # the CACHEBUSTER to the PR number. build --action_env=CACHEBUSTER=20220325 # Use Python 3.X as installed in container image
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Tue Nov 21 12:25:39 GMT 2023 - 6.3K bytes - Viewed (0) -
CONTRIBUTING.md
to the core. * As every PR requires several CPU/GPU hours of CI testing, we discourage submitting PRs to fix one typo, one warning,etc. We recommend fixing the same issue at the file level at least (e.g.: fix all typos in a file, fix all compiler warnings in a file, etc.) * Tests should follow the [testing best practices](https://www.tensorflow.org/community/contribute/tests) guide.
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Mar 21 11:45:51 GMT 2024 - 15.6K bytes - Viewed (0) -
ci/official/containers/linux_arm64/Dockerfile
COPY devel.packages.txt /devel.packages.txt COPY cuda.packages.txt /cuda.packages.txt RUN /setup.sources.sh && /setup.packages.sh /devel.packages.txt # Install various tools. # - bats: bash unit testing framework # NOTE: v1.6.0 seems to have a bug that made "git" in setup_file break # - bazelisk: always use the correct bazel version # - buildifier: clean bazel build deps # - buildozer: clean bazel build deps
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Mon Jan 08 09:32:19 GMT 2024 - 4.1K bytes - Viewed (1) -
SECURITY.md
Compiling models via the recommended entry points described in [XLA](https://www.tensorflow.org/xla) and [JAX](https://jax.readthedocs.io/en/latest/jax-101/02-jitting.html) documentation should be safe, while some of the testing and debugging tools that come with the compiler are not designed to be used with untrusted data and should be used with caution when working with untrusted models. ### Saved graphs and checkpoints
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Sun Oct 01 06:06:35 GMT 2023 - 9.6K bytes - Viewed (0) -
.bazelrc
common:rbe_linux_cpu_old --remote_instance_name=projects/tensorflow-testing/instances/default_instance build:rbe_linux_cuda --config=cuda_clang_official build:rbe_linux_cuda --config=rbe_linux_cpu # For Remote build execution -- GPU configuration build:rbe_linux_cuda --repo_env=REMOTE_GPU_TESTING=1 build:rbe_linux_cuda --repo_env=TF_CUDA_CONFIG_REPO="@sigbuild-r2.17-clang_config_cuda"
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu May 02 19:34:20 GMT 2024 - 52.8K bytes - Viewed (2) -
tensorflow/BUILD
# Non-configurable setting to indicate open source build. bool_setting( name = "oss_setting", build_setting_default = if_oss(True, False), visibility = ["//visibility:private"], ) # Setting to use when loading kernels dynamically config_setting( name = "dynamic_loaded_kernels", define_values = { "dynamic_loaded_kernels": "true", "framework_shared_object": "true", },
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Tue Apr 09 18:15:11 GMT 2024 - 53.4K bytes - Viewed (8) -
RELEASE.md
If you experience any snags when using TF 2.0, please let us know at the [TF 2.0 Testing User Group](https://groups.google.com/a/tensorflow.org/forum/?utm_medium=email&utm_source=footer#!forum/testing). We have a support mailing list as well as weekly testing meetings, and would love to hear your migration feedback and questions. ## Bug Fixes and Other Changes * `tf.contrib`:
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Mon Apr 29 19:17:57 GMT 2024 - 727.7K bytes - Viewed (8)