Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for locality (0.15 sec)

  1. ci/official/wheel_test/README.md

    [requirements updater readme](https://github.com/tensorflow/tensorflow/blob/master/ci/official/requirements_updater/README.md)
    
    ### Prerequisites for Local Testing
    
    To run tests locally, follow these steps:
    
    1.  Navigate to the relevant directory:
        ```
        cd ci/official/wheel_test
        ```
    2.  Run a script for creating requirements file:
        ```
    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)
  2. ci/official/README.md

    ## How to Test Your Changes to TensorFlow
    
    You may check how your changes will affect TensorFlow by:
    
    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
    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)
  3. CONTRIBUTING.md

        [TensorFlow Builds](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/tools/ci_build)
        for details.
    
    #### Running doctest for testable docstring
    
    There are two ways to test the code in the docstring locally:
    
    1.  If you are only changing the docstring of a class/function/method, then you
        can test it by passing that file's path to
        [tf_doctest.py](https://www.tensorflow.org/code/tensorflow/tools/docs/tf_doctest.py).
    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)
  4. tensorflow/c/eager/c_api_experimental.h

    // EagerService to maintain consistency between client and worker. The
    // context_id is initialized with a dummy value and is later set when the worker
    // is initialized (either locally or remotely). The context_id can change during
    // the process lifetime although this should cause the worker to be
    // reinitialized (e.g. cleared caches) as well.
    TF_CAPI_EXPORT extern uint64_t TFE_GetContextId(TFE_Context* ctx);
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Feb 21 22:37:46 GMT 2024
    - 39.5K bytes
    - Viewed (0)
  5. .bazelrc

    # leading to build failures. To resolve the issue, the following line is added
    # to make sure all Genrule targets are excuted locally.
    build:rbe_cross_compile_base_xla --config=rbe_cross_compile_base
    build:rbe_cross_compile_base_xla --strategy=Genrule=standalone
    
    # Due to the above strategy, all Genrule commands are executed locally, but the
    # following actions invoke tools (E.g `flatc`, `llvm-tblgen`, etc.) that are
    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. configure.py

      if not is_linux():
        raise ValueError('Currently NCCL is only supported on Linux platform.')
    
      if 'TF_NCCL_VERSION' in environ_cp:
        return
    
      ask_nccl_version = (
          'Please specify the locally installed NCCL version you want to use. '
          '[Leave empty to use http://github.com/nvidia/nccl]: ')
      tf_nccl_version = get_from_env_or_user_or_default(environ_cp,
    Python
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Mon Apr 15 18:25:36 GMT 2024
    - 53.8K bytes
    - Viewed (1)
  7. ci/official/utilities/setup.sh

    # $TFCI_OUTPUT_DIR/script.log
    exec > >(tee "$TFCI_OUTPUT_DIR/script.log") 2>&1
    
    # Setup tfrun, a helper function for executing steps that can either be run
    # locally or run under Docker. setup_docker.sh, below, redefines it as "docker
    # exec".
    # Important: "tfrun foo | bar" is "( tfrun foo ) | bar", not "tfrun (foo | bar)".
    # Therefore, "tfrun" commands cannot include pipes -- which is
    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)
Back to top