Skip to content

Commit

Permalink
Resolved merge conflicts
Browse files Browse the repository at this point in the history
  • Loading branch information
mahmoud-abuzaina committed Nov 16, 2023
2 parents e67bb7f + 8f8b548 commit dbc7100
Show file tree
Hide file tree
Showing 3,083 changed files with 132,801 additions and 71,724 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
134 changes: 104 additions & 30 deletions .bazelrc

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion .github/bot_config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ assignees:
- sushreebarsa
- SuryanarayanaY
- tilakrayal
- Varsha-anjanappa
- Venkat6871
# A list of assignees for compiler folder
compiler_assignees:
- joker-eph
Expand Down
39 changes: 39 additions & 0 deletions .github/workflows/osv-scanner-scheduled.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# Copyright 2023 The TensorFlow Authors. All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# ==============================================================================

name: OSV-Scanner Scheduled Scan

on:
schedule:
- cron: 0 4 * * 1

permissions:
# Require writing security events to upload SARIF file to security tab
security-events: write
# Only need to read contents
contents: read

jobs:
scan-scheduled:
uses: "google/osv-scanner/.github/workflows/osv-scanner-reusable.yml@main"
with:
scan-args: |-
--lockfile=requirements.txt:./requirements_lock_3_9.txt
--lockfile=requirements.txt:./requirements_lock_3_10.txt
--lockfile=requirements.txt:./requirements_lock_3_11.txt
--lockfile=requirements.txt:./requirements_lock_3_12.txt
--lockfile=requirements.txt:./ci/official/containers/linux_arm64/devel.requirements.txt
--lockfile=requirements.txt:./ci/official/containers/linux_arm64/jax.requirements.txt
--lockfile=requirements.txt:./ci/official/containers/linux_arm64/devel.usertools/test.requirements.txt
2 changes: 1 addition & 1 deletion .github/workflows/sigbuild-docker-branch.yml
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
python-version: [python3.9, python3.10, python3.11]
python-version: [python3.9, python3.10, python3.11, python3.12]
steps:
- name: Delete unnecessary tools folder
run: rm -rf /opt/hostedtoolcache
Expand Down
3 changes: 2 additions & 1 deletion .github/workflows/sigbuild-docker-presubmit.yml
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
python-version: [python3.9, python3.10, python3.11]
python-version: [python3.9, python3.10, python3.11, python3.12]
permissions:
contents: read
pull-requests: write
Expand Down Expand Up @@ -87,6 +87,7 @@ jobs:
message: |
I pushed these containers:
- `gcr.io/tensorflow-sigs/build:${{ github.event.number }}-python3.12`
- `gcr.io/tensorflow-sigs/build:${{ github.event.number }}-python3.11`
- `gcr.io/tensorflow-sigs/build:${{ github.event.number }}-python3.10`
- `gcr.io/tensorflow-sigs/build:${{ github.event.number }}-python3.9`
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/sigbuild-docker.yml
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
python-version: [python3.9, python3.10, python3.11]
python-version: [python3.9, python3.10, python3.11, python3.12]
steps:
- name: Delete unnecessary tools folder
run: rm -rf /opt/hostedtoolcache
Expand Down
12 changes: 12 additions & 0 deletions .github/workflows/update-rbe.yml
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,18 @@ jobs:
map sigbuild-r2.14-clang-python3.9 2.14-python3.9
map sigbuild-r2.14-clang-python3.10 2.14-python3.10
map sigbuild-r2.14-clang-python3.11 2.14-python3.11
# TF 2.16
map sigbuild-r2.16 2.16-python3.9
map sigbuild-r2.16-python3.9 2.16-python3.9
map sigbuild-r2.16-python3.10 2.16-python3.10
map sigbuild-r2.16-python3.11 2.16-python3.11
map sigbuild-r2.16-python3.12 2.16-python3.12
# TF 2.16 + Clang (containers are the same, but env vars in configs.bzl are different)
map sigbuild-r2.16-clang 2.16-python3.9
map sigbuild-r2.16-clang-python3.9 2.16-python3.9
map sigbuild-r2.16-clang-python3.10 2.16-python3.10
map sigbuild-r2.16-clang-python3.11 2.16-python3.11
map sigbuild-r2.16-clang-python3.12 2.16-python3.12
- name: Create Pull Request with changes
uses: peter-evans/create-pull-request@2b011faafdcbc9ceb11414d64d0573f37c774b04 # v4.2.3
with:
Expand Down
17 changes: 12 additions & 5 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,8 +89,8 @@ Follow either of the two links above to access the appropriate CLA and instructi
### Contributing code

If you have improvements to TensorFlow, send us your pull requests! For those
just getting started, Github has a
[how to](https://help.github.com/articles/using-pull-requests/).
just getting started, GitHub has a
[how-to](https://help.github.com/articles/using-pull-requests/).

TensorFlow team members will be assigned to review your pull requests. Once the
pull requests are approved and pass continuous integration checks, a TensorFlow
Expand All @@ -101,7 +101,7 @@ automatically on GitHub.

If you want to contribute, start working through the TensorFlow codebase,
navigate to the
[Github "issues" tab](https://github.com/tensorflow/tensorflow/issues) and start
[GitHub "issues" tab](https://github.com/tensorflow/tensorflow/issues) and start
looking through interesting issues. If you are not sure of where to start, then
start by trying one of the smaller/easier issues here i.e.
[issues with the "good first issue" label](https://github.com/tensorflow/tensorflow/labels/good%20first%20issue)
Expand Down Expand Up @@ -232,13 +232,20 @@ There are two ways to run TensorFlow unit tests.
and
[GPU developer Dockerfile](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/dockerfiles/dockerfiles/devel-gpu.Dockerfile)
for the required packages. Alternatively, use the said
[Docker images](https://hub.docker.com/r/tensorflow/tensorflow/tags/), e.g.,
`tensorflow/tensorflow:devel` and `tensorflow/tensorflow:devel-gpu` for
[tensorflow/build Docker images](https://hub.docker.com/r/tensorflow/build)
(`tensorflow/tensorflow:devel` and `tensorflow/tensorflow:devel-gpu` are no
longer supported for) development. Use TF SIG Build Dockerfiles in
development to avoid installing the packages directly on your system (in
which case remember to change the directory from `/root` to `/tensorflow`
once you get into the running container so `bazel` can find the `tensorflow`
workspace).

you can do this by using the following command. As an example-

```bash
docker run -it --rm -v $PWD:/tmp -w /tmp tensorflow/build:2.15-python3.10
```

Once you have the packages installed, you can run a specific unit test in
bazel by doing as follows:

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ apply fixes to bugs or security vulnerabilities:

* Clone the TensorFlow repo and switch to the corresponding branch for your
desired TensorFlow version, for example, branch `r2.8` for version 2.8.
* Apply (that is, cherry pick) the desired changes and resolve any code
* Apply (that is, cherry-pick) the desired changes and resolve any code
conflicts.
* Run TensorFlow tests and ensure they pass.
* [Build](https://www.tensorflow.org/install/source) the TensorFlow pip
Expand Down
Loading

0 comments on commit dbc7100

Please sign in to comment.