Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for gdscript (0.22 sec)

  1. ci/official/wheel_test/README.md

        ```
        cd ci/official/wheel_test
        ```
    2.  Run a script for creating requirements file:
        ```
        bash update_requirements.sh <path_to_tensorflow_wheel> <python_version>
        e.g.:
        bash update_requirements.sh /tmp/tensorflow-2.14.0-cp311-cp311-linux_x86_64.whl 3_11
        ```
    
    #### Requirements Updater Script
    This script automates the process of updating TensorFlow requirements for a
    specific Python version.
    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

    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
    
    # Here is a single-line example of running a script on Linux to build the
    # GPU version of TensorFlow for Python 3.12, using the public TF bazel cache and
    # a local build cache:
    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. ci/official/requirements_updater/README.md

       `release_updater.sh`
    
    5) Run the `updater.sh` shell script. \
       If the base requirements file hasn't yet been updated to account for the new
       Python version, which will require different versions for at least some
       dependencies, it will need to be updated now, for the script to run
       successfully.
    
    6) A new `requirements_lock_3_11.txt` file should appear under the root of the
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Tue Jan 23 02:14:00 GMT 2024
    - 3.9K bytes
    - Viewed (1)
Back to top