- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 67 for bazel (0.04 sec)
-
ci/official/requirements_updater/BUILD.bazel
Vadym Matsishevskyi <******@****.***> 1719618893 -0700
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Sat Jun 29 00:19:18 UTC 2024 - 1K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/aarch64.bazelrc
# installed into a virtual environment, and then that venv is used to run all # bazel tests with a special flag "--define=no_tensorflow_py_deps=true", which # drops all the bazel dependencies for each py_test; this makes all the tests # use the wheel's TensorFlow installation instead of the one made available # through bazel. This must be done in a different root directory, //bazel_pip/...,
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Fri Jul 12 20:16:57 UTC 2024 - 5.7K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/aarch64_clang.bazelrc
# installed into a virtual environment, and then that venv is used to run all # bazel tests with a special flag "--define=no_tensorflow_py_deps=true", which # drops all the bazel dependencies for each py_test; this makes all the tests # use the wheel's TensorFlow installation instead of the one made available # through bazel. This must be done in a different root directory, //bazel_pip/...,
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Fri Jul 12 20:16:57 UTC 2024 - 6.2K bytes - Viewed (0) -
CONTRIBUTING.md
once you get into the running container so `bazel` can find the `tensorflow` workspace). you can do this by using the following command. As an example- ```bash docker run -it --rm -v $PWD:/tmp -w /tmp tensorflow/build:2.15-python3.10 ``` Once you have the packages installed, you can run a specific unit test in bazel by doing as follows: ```bash
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Oct 23 06:20:12 UTC 2024 - 15.9K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/code_check_changed_files.bats
setup_file() { cd /tf/tensorflow bazel version # Start the bazel server # Without this, git errors if /tf/tensorflow directory owner is different git config --global --add safe.directory /tf/tensorflow # Note that you could generate a list of all the affected targets with e.g.: # bazel query $(paste -sd "+" $BATS_FILE_TMPDIR/changed_files) --keep_going
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Mon Sep 18 14:52:45 UTC 2023 - 3.6K bytes - Viewed (0) -
ci/official/utilities/repack_libtensorflow.sh
rm -rf "${tmp_dir}" } DIR=$1 TARBALL_SUFFIX=$2 mkdir -p "$DIR" cp bazel-bin/tensorflow/tools/lib_package/libtensorflow.tar.gz "${DIR}/libtensorflow${TARBALL_SUFFIX}.tar.gz" cp bazel-bin/tensorflow/tools/lib_package/libtensorflow_jni.tar.gz "${DIR}/libtensorflow_jni${TARBALL_SUFFIX}.tar.gz" cp bazel-bin/tensorflow/java/libtensorflow.jar "${DIR}" cp_normalized_srcjar bazel-bin/tensorflow/java/libtensorflow-src.jar "${DIR}/libtensorflow-src.jar"
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Jul 12 19:47:53 UTC 2023 - 2.6K bytes - Viewed (0) -
ci/official/requirements_updater/README.md
you wish the updater to consider pre-release versions simply pass `--pre` argument to the bazel command: ``` bazel run //ci/official/requirements_updater:requirements.update --repo_env=HERMETIC_PYTHON_VERSION=3.12 -- --pre ``` If you need to upgrade all of the packages in requirements lock file, just pass the `--upgrade` parameter: ```
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Sat Jun 29 00:19:18 UTC 2024 - 3K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/code_check_full.bats
# anything with a Windows-only toolchain, and bazel errors if trying to build # that directory. @test "bazel nobuild passes on all of TF except TF Lite and win toolchains" { bazel build --experimental_cc_shared_library --nobuild --keep_going -- //tensorflow/... -//tensorflow/lite/... -//tensorflow/tools/toolchains/win/... -//tensorflow/tools/toolchains/win_1803/... } teardown_file() { bazel shutdown
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Aug 14 18:47:44 UTC 2024 - 12.9K bytes - Viewed (0) -
ci/official/containers/ml_build/Dockerfile
# Make sure clang is on the path RUN ln -s /usr/lib/llvm-18/bin/clang /usr/bin/clang # Install various tools. # - bats: bash unit testing framework # - bazelisk: always use the correct bazel version # - buildifier: clean bazel build deps # - buildozer: clean bazel build deps # - gcloud SDK: communicate with Google Cloud Platform (GCP) for RBE, CI # - patchelf: Utility tool to modify existing ELF executables and libraries
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Oct 30 00:07:17 UTC 2024 - 3.8K bytes - Viewed (0) -
ci/official/pycpp.sh
fi if [[ $TFCI_PYCPP_SWAP_TO_BUILD_ENABLE == 1 ]]; then tfrun bazel build $TFCI_BAZEL_COMMON_ARGS --profile "$PROFILE_JSON_PATH" --@local_config_cuda//cuda:override_include_cuda_libs=true --config="${TFCI_BAZEL_TARGET_SELECTING_CONFIG_PREFIX}_pycpp_test" else
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Oct 23 18:48:35 UTC 2024 - 1.9K bytes - Viewed (0)