Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for funding (0.16 sec)

  2. github.com/tensorflow/tensorflow

    README.md 

    [![Fuzzing Status](https://oss-fuzz-build-logs.storage.googleapis.com/badges/tensorflow.svg)](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:tensorflow)
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Oct 05 15:00:10 GMT 2023
    - 11.9K bytes
    - Viewed (0)
  3. github.com/tensorflow/tensorflow

    ci/official/README.md 

    You may check how your changes will affect TensorFlow by:

1. Creating a PR and observing the presubmit test results
2. Running the CI scripts locally, as explained below
3. **Google employees only**: Google employees can use an internal-only tool
called "MLCI" that makes testing more convenient: it can execute any full CI job
against a pending change. Search for "MLCI" internally to find it.
    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)
  4. github.com/tensorflow/tensorflow

    ci/official/requirements_updater/README.md 

    unless indicated otherwise.

1) Add the new version to the `VERSIONS` variable inside
   `tensorflow/tools/toolchains/python/python_repo.bzl`. \
   While this isn't necessary for running the updater, it is required for
   actually using the new version with Tensorflow.

2) In the `WORKSPACE` file, add the new version to the `python_versions`
   parameter of the `python_register_multi_toolchains` function.
    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