Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for Valid (7.77 sec)

  1. ci/official/envs/rbe

    # TFCI_BAZEL_TARGET_SELECTING_CONFIG_PREFIX. "Available" means there is
    # an entry in tensorflow/.bazelrc for build:rbe_TFCI_BAZEL_TARGET...
    #                                           ^^^^
    # This env is only valid when RBE is available on the selected platform, since
    # it enables a derived --config setting.  If RBE is not available (i.e. there
    # is no --config setting), bazel would fail and quit. This script does a quick
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Jan 10 19:39:41 GMT 2024
    - 2K bytes
    - Viewed (0)
  2. CONTRIBUTING.md

      `comp:` etc.  At this stage we check if the PR is valid and meets certain
      quality requirements. For example, we check if the CLA is signed, PR has
      sufficient description, if applicable unit tests are added, if it is a
      reasonable contribution (meaning it is not a single liner cosmetic PR).
    
    **2. Valid?**
    
    -   If the PR passes all the quality checks then we go ahead and assign a
        reviewer.
    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. ci/official/containers/linux_arm64/devel.usertools/code_check_full.bats

    #
    # 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.
    @test "bazel nobuild passes on all of TF except TF Lite and win toolchains" {
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Mon Sep 18 14:52:45 GMT 2023
    - 12.7K bytes
    - Viewed (0)
  4. ci/official/utilities/code_check_full.bats

    #
    # 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.
    @test "bazel nobuild passes on all of TF except TF Lite and win toolchains" {
    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. RELEASE.md

            *   Using `functools.wraps` on a function with different signature
            *   Using `functools.partial` with an invalid `tf.function` input
        *   `tf.function` now enforces input parameter names to be valid Python identifiers. Incompatible names are automatically sanitized similarly to existing SavedModel signature behavior.
    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