Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for something (3.99 sec)

  1. ci/official/containers/linux_arm64/devel.usertools/aarch64.bazelrc

    # "pip tests" run a similar suite of tests the "nonpip" tests, but do something
    # odd to attempt to validate the quality of the pip package. The wheel is
    # 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
    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)
  2. ci/official/containers/linux_arm64/devel.usertools/aarch64_clang.bazelrc

    # "pip tests" run a similar suite of tests the "nonpip" tests, but do something
    # odd to attempt to validate the quality of the pip package. The wheel is
    # 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
    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)
  3. ci/official/utilities/setup.sh

    # exec".
    # Important: "tfrun foo | bar" is "( tfrun foo ) | bar", not "tfrun (foo | bar)".
    # Therefore, "tfrun" commands cannot include pipes -- which is
    # probably for the better. If a pipe is necessary for something, it is probably
    # complex. Write a well-documented script under utilities/ to encapsulate the
    # functionality instead.
    tfrun() { "$@"; }
    
    # Run all "tfrun" commands under Docker. See setup_docker.sh for details
    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)
  4. ci/official/utilities/code_check_full.bats

    # checks for cross-file issues like bad includes or missing BUILD definitions.
    #
    # We can't test on the windows toolchains because they're using a legacy
    # toolchain format (or something) that specifies the toolchain directly instead
    # of as a "repository". They can't be valid on Linux because Linux can't do
    # anything with a Windows-only toolchain, and bazel errors if trying to build
    # that directory.
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Mar 06 21:54:13 GMT 2024
    - 13.2K bytes
    - Viewed (0)
  5. .bazelrc

    build:windows --host_linkopt=/DEBUG
    build:windows --linkopt=/OPT:REF
    build:windows --host_linkopt=/OPT:REF
    build:windows --linkopt=/OPT:ICF
    build:windows --host_linkopt=/OPT:ICF
    
    # Verbose failure logs when something goes wrong
    build:windows --verbose_failures
    
    # Work around potential issues with large command lines on windows.
    # See: https://github.com/bazelbuild/bazel/issues/5163
    build:windows --features=compiler_param_file
    
    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)
  6. RELEASE.md

    *   Performance improvements for gRPC
    *   Improved support for fp16
    *   New high-level ops in tf.contrib. {layers,metrics}
    *   New features for TensorBoard, such as shape display, exponential smoothing
    *   Faster and more stable Google Cloud Storage (GCS) filesystem support
    *   Support for zlib compression and decompression for TFRecordReader and
        TFRecordWriter
    *   Support for reading (animated) GIFs
    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)
Back to top