- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Variable (0.17 sec)
-
ci/official/wheel_test/README.md
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 ``` bazel build //:test_import_api_packages ``` ##### How to Run ``` bazel test //:test_import_api_packages --test_output=all
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) -
ci/official/requirements_updater/README.md
Note: Only a number of minor Python versions are supported at any given time. By default, the lowest supported version is used. To set a different version, use the `TF_PYTHON_VERSION` environment variable, e.g. ``` export TF_PYTHON_VERSION=3.11 ``` To specify the version via a Bazel command argument, use the following: ``` --repo_env=TF_PYTHON_VERSION=3.11 ``` ## Requirements updater
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) -
ci/official/README.md
is a brief explanation of how they tie together: 1. `envs/*` are lists of variables made with bash syntax. A user must set a `TFCI` env param pointing to a list of `env` files. 2. `utilities/setup.sh`, initialized by all top-level scripts, reads and sets values from those `TFCI` paths. - `set -a` / `set -o allexport` exports the variables from `env` files so all scripts can use them.
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)