Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for teksting (1.97 sec)

  1. 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)
  2. 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)
  3. tensorflow/BUILD

    #     visibility = ["//visibility:public"],
    # )
    #
    # filegroup(
    #     name = "copybara_config",
    #     srcs = ["copy.bara.sky"],
    #     data = [
    #         ":copybara_library",
    #         "//learning/brain/testing/copybara:all_bara_sky",
    #         "//third_party/tsl:copybara_library",
    #         "//third_party/xla:copybara_library",
    #     ],
    #     visibility = ["//visibility:public"],
    # )
    #
    # copybara_config_test(
    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)
  4. 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)
  5. 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)
  6. .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)
Back to top