Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 61 for directly (0.7 sec)

  1. ci/official/wheel_test/README.md

    init files creation process and is subsequently stored in the wheel file after
    the build. It also contains a few paths that cannot be directly imported. These
    paths point to attributes or sub-modules within a module's namespace, but they
    don't correspond to an actual file or directory on the filesystem. The list of
    such paths is stored in the packages_for_skip variable and will be skipped
    during the test.
    
    ##### How to Build
    
    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/containers/linux_arm64/devel.usertools/aarch64.bazelrc

    # use the wheel's TensorFlow installation instead of the one made available
    # through bazel. This must be done in a different root directory, //bazel_pip/...,
    # because "import tensorflow" run from the root directory would instead import
    # the folder instead of the venv package.
    # 
    # Pass --config=pip to run the same suite of tests. If you want to run just one
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Tue Nov 21 12:25:39 GMT 2023
    - 5.8K bytes
    - Viewed (0)
  3. tensorflow/c/experimental/filesystem/modular_filesystem_test.cc

        s = fs->CreateDir(root_dir_);
        if (!s.ok()) {
          GTEST_SKIP() << "Cannot create working directory: " << s;
        }
      }
    
      // Converts path reference to URI reference.
      //
      // If URI scheme is empty, URI reference is `path` relative to current test
      // root directory. Otherwise, we need to add the `<scheme>://` in front of
      // this path.
      //
    C++
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Fri May 27 20:25:58 GMT 2022
    - 71K bytes
    - Viewed (0)
  4. tensorflow/c/experimental/filesystem/modular_filesystem.cc

        stat->length = stats.length;
        stat->mtime_nsec = stats.mtime_nsec;
        stat->is_directory = stats.is_directory;
      }
    
      return StatusFromTF_Status(plugin_status.get());
    }
    
    Status ModularFileSystem::IsDirectory(const std::string& name,
                                          TransactionToken* token) {
      if (ops_->is_directory == nullptr)
        return FileSystem::IsDirectory(name, token);
    
    C++
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Sep 06 19:12:29 GMT 2023
    - 23.1K bytes
    - Viewed (0)
  5. ci/official/containers/linux_arm64/devel.usertools/repack_libtensorflow.sh

    # and also repacks libtensorflow-src.jar into a standardized format.
    
    # Helper function to copy a srcjar after moving any source files
    # directly under the root to the "maven-style" src/main/java layout
    #
    # Source files generated by annotation processors appear directly
    # under the root of srcjars jars created by bazel, rather than under
    # the maven-style src/main/java subdirectory.
    #
    Shell Script
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Mon Sep 18 14:52:45 GMT 2023
    - 2.6K bytes
    - Viewed (0)
  6. ci/official/utilities/code_check_changed_files.bats

    setup_file() {
        bazel version  # Start the bazel server
    
        # Fixes "fatal: detected dubious ownership in repository" for Docker.
        git config --system --add safe.directory '*'
        git config --system protocol.file.allow always
    
        # Note that you could generate a list of all the affected targets with e.g.:
        # bazel query $(paste -sd "+" $BATS_FILE_TMPDIR/changed_files) --keep_going
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Jan 10 19:39:41 GMT 2024
    - 4K bytes
    - Viewed (0)
  7. ci/official/utilities/repack_libtensorflow.sh

    # and also repacks libtensorflow-src.jar into a standardized format.
    
    # Helper function to copy a srcjar after moving any source files
    # directly under the root to the "maven-style" src/main/java layout
    #
    # Source files generated by annotation processors appear directly
    # under the root of srcjars jars created by bazel, rather than under
    # the maven-style src/main/java subdirectory.
    #
    Shell Script
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Jul 12 19:47:53 GMT 2023
    - 2.6K bytes
    - Viewed (0)
  8. tensorflow/c/experimental/filesystem/modular_filesystem_registration.h

    #include "tensorflow/core/platform/status.h"
    
    namespace tensorflow {
    namespace filesystem_registration {
    
    // Implementation for filesystem registration
    //
    // Don't call this directly. Instead call `RegisterFilesystemPlugin`.
    // Exposed only for static registration of local filesystems.
    Status RegisterFilesystemPluginImpl(const TF_FilesystemPluginInfo* info);
    
    }  // namespace filesystem_registration
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Fri Mar 20 16:42:12 GMT 2020
    - 1.4K bytes
    - Viewed (0)
  9. tensorflow/c/eager/immediate_execution_context.h

      // Register a custom device. It will return error is the device name is
      // already registered.
      // TODO(tfrt-devs): Remove this method. Let caller register it directly into
      // CustomDeviceOpHandler.
      virtual Status RegisterCustomDevice(const string& name,
                                          std::unique_ptr<CustomDevice> device) = 0;
    
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Jul 06 08:34:00 GMT 2023
    - 12.3K bytes
    - Viewed (0)
  10. tensorflow/c/experimental/filesystem/plugins/gcs/cleanup.h

    //     while (ReadDataObject(fp, &d)) {
    //       if (d.IsBad()) {
    //         LOG(ERROR) << "Bad Data";
    //         return;
    //       }
    //       PushGoodData(d);
    //     }
    //   }
    //
    // You can use Cleanup<F> directly, instead of using MakeCleanup and auto,
    // but there's rarely a reason to do that.
    //
    // You can call 'release()' on a Cleanup object to cancel the cleanup.
    
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Jul 09 11:16:00 GMT 2020
    - 3.4K bytes
    - Viewed (0)
Back to top