Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for ACTIVATE (0.2 sec)

  1. ci/official/containers/linux_arm64/devel.usertools/wheel_verification.bats

    # up in teardown_file() above.
    @test "Wheel is installable" {
        python3 -m venv /tf/venv
        source /tf/venv/bin/activate
        python3 -m pip install --upgrade setuptools wheel
        python3 -m pip install "$TF_WHEEL"
    }
    
    @test "TensorFlow is importable" {
        source /tf/venv/bin/activate
        python3 -c 'import tensorflow as tf; t1=tf.constant([1,2,3,4]); t2=tf.constant([5,6,7,8]); print(tf.add(t1,t2).shape)'
    }
    
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Tue Jan 23 02:14:00 GMT 2024
    - 2.7K bytes
    - Viewed (0)
  2. ci/official/utilities/setup_macos.sh

      # Python 3.12 removed the module `imp` which is needed by gcloud CLI so we set
      # `CLOUDSDK_PYTHON` to Python 3.11 which is the system Python on TFCI Mac
      # VMs.
      export CLOUDSDK_PYTHON=$(which python3.11)
      gcloud auth activate-service-account --key-file="${GOOGLE_APPLICATION_CREDENTIALS}"
    fi
    set -x
    
    # When cross-compiling with RBE, we need to copy the macOS sysroot to be
    Shell Script
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Feb 15 15:23:28 GMT 2024
    - 6.2K bytes
    - Viewed (0)
  3. ci/official/upload.sh

    # gs://tensorflow/nightly/2.16.0-dev20240105 (nightly), overwriting previous values.
    if [[ "$TFCI_ARTIFACT_FINAL_GCS_ENABLE" == 1 ]]; then
      gcloud auth activate-service-account --key-file="$TFCI_ARTIFACT_FINAL_GCS_SA_PATH"
    
      # $TF_VER_FULL will resolve to e.g. "2.15.0-rc2". Since $TF_VER_FULL comes
      # from get_versions.sh, which must be run *after* update_version.py, FINAL_URI
    Shell Script
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Jan 24 20:52:12 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  4. tensorflow/c/eager/tape.h

        //
        // Rather than re-entering and delegating Accumulate like this, we could
        // instead allow ForwardAccumulator some control over the current tape set
        // (so it can deactivate itself and activate its GradientTape). Currently
        // that is managed by the language binding and would require relatively
        // messy callbacks.
        call_state_.top().backward_tape->RecordOperation(
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Tue Apr 02 12:40:29 GMT 2024
    - 47.2K bytes
    - Viewed (1)
Back to top