- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 25 for Every (0.13 sec)
-
ci/official/README.md
- Nightly jobs (Run nightly on the `nightly` branch) - Uses `wheel.sh`, `libtensorflow.sh`, `code_check_full.sh` - Continuous jobs (Run on every GitHub commit) - Uses `pycpp.sh` - Presubmit jobs (Run on every GitHub PR) - Uses `pycpp.sh`, `code_check_changed_files.sh` These "env" files match up with an environment matrix that roughly covers: - Different Python versions
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) -
tensorflow/c/experimental/next_pluggable_device/c_api.h
typedef struct TF_VariableInfo TF_VariableInfo; // Returns a `TF_Device` pointer, which actually points to a C++ `Device`. // Currently we only allow `NextPluggableDevice` to be casted as `TF_Device`, // but in theory every this is a C API for every kind of device. TF_CAPI_EXPORT extern TF_Device* TF_GetDevice(TF_OpKernelContext* ctx); // -------------------------- Resource ---------------------------------------
C - Registered: Tue Feb 27 12:39:08 GMT 2024 - Last Modified: Wed Dec 20 20:01:06 GMT 2023 - 7.2K bytes - Viewed (0) -
CONTRIBUTING.md
### Typical Pull Request Workflow - **1. New PR** - As a contributor, you submit a New PR on GitHub. - We inspect every incoming PR and add certain labels to the PR such as `size:`, `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
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) -
tensorflow/c/experimental/filesystem/modular_filesystem_test.cc
// // Each filesystem implementation can be provided by DSOs, so we provide the // `--dsos` flag to specify a list of shared objects to be loaded in order. // If the flag is not used, no shared objects are loaded. // // Every filesystem provides support for accessing URIs of form // `[<scheme>://]<path>` where `<scheme>` is optional (if missing, we are // accessing local paths). This test suite tests exactly one scheme for each
C++ - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Fri May 27 20:25:58 GMT 2022 - 71K bytes - Viewed (0) -
ci/official/utilities/setup.sh
# variables in it, OR may be left empty if the user has already exported the # relevant variables in their environment. Because of 'set -o allexport' above # (which is equivalent to "set -a"), every variable in the file is exported # for other files to use. # # Separately, if TFCI is set *and* there are also additional TFCI_ variables # set in the shell environment, those variables will be restored after the
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) -
ci/official/utilities/code_check_full.bats
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/tf_sig_build_dockerfiles/devel.usertools/code_check_full.bats Here are the affected tests: EOF while read dep; do echo "For dependency $dep:" # For every missing dependency, find the tests which directly depend on # it, and print that list for debugging. Not really clear if this is # helpful since the only examples I've seen are enormous.
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) -
tensorflow/c/experimental/filesystem/filesystem_interface.h
/// /// Both core TensorFlow and every plugin will use this header. The associated /// `.cc` file is only used by core TensorFlow to implement checking needed for /// plugin registration and ensuring API and ABI compatibility. Plugin authors /// don't need to read the `.cc` file but they should consult every section of /// this file to ensure a compliant plugin can be built and that the plugin can
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Fri May 27 17:36:54 GMT 2022 - 53.1K bytes - Viewed (0) -
ci/official/containers/linux_arm64/devel.usertools/code_check_full.bats
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/tf_sig_build_dockerfiles/devel.usertools/code_check_full.bats Here are the affected tests: EOF while read dep; do echo "For dependency $dep:" # For every missing dependency, find the tests which directly depend on # it, and print that list for debugging. Not really clear if this is # helpful since the only examples I've seen are enormous.
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) -
ci/official/envs/ci_default
# ============================================================================== # Note: this file gets sourced in utilities/setup.sh, which has "set -u" # (error on undefined variables). This ensures that (a) every TFCI variable # has an explicit default value, and (b) no script can accidentally use a # variable that doesn't exist. Please keep this list in alphabetical order. # # Find usage in scripts with e.g.: # cd ci/official
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Mar 27 21:16:27 GMT 2024 - 2.5K bytes - Viewed (0) -
tensorflow/c/eager/c_api.h
// graph mode). Calling this on a context tells it to start a step. TF_CAPI_EXPORT extern void TFE_ContextStartStep(TFE_Context* ctx); // Ends a step. When there is no active step (that is, every started step has // been ended) step containers will be cleared. Note: it is not safe to call // TFE_ContextEndStep while ops that rely on the step container may be running.
C - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Apr 27 21:07:00 GMT 2023 - 22.8K bytes - Viewed (1)