Skip to content

Add models test for android and iOS#74947

Closed
linbinyu wants to merge 2 commits intomasterfrom
linbin/test_models
Closed

Add models test for android and iOS#74947
linbinyu wants to merge 2 commits intomasterfrom
linbin/test_models

Conversation

@linbinyu
Copy link
Copy Markdown
Contributor

See #74793 for more details
Redo everything in one pr. This diff added test model generation script and updated android and ios tests.

@facebook-github-bot
Copy link
Copy Markdown
Contributor

facebook-github-bot commented Mar 30, 2022

🔗 Helpful links

💊 CI failures summary and remediations

As of commit b633db1 (more details on the Dr. CI page):



🕵️ 5 new failures recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

See GitHub Actions build pull / linux-xenial-cuda11.3-py3.7-gcc7 / build (1/5)

Step: "Build" (full log | diagnosis details | 🔁 rerun)

2022-03-30T17:52:59.2573769Z �[36;1m echo "ERR...t available for the merge-base of your branch"�[0m
2022-03-30T17:52:59.2570947Z �[36;1mfi�[0m
2022-03-30T17:52:59.2571171Z �[36;1m# Covers the case where a previous tag doesn't exist for the tree�[0m
2022-03-30T17:52:59.2571509Z �[36;1m# this is only really applicable on trees that don't have `.circleci/docker` at its merge base, i.e. nightly�[0m
2022-03-30T17:52:59.2571818Z �[36;1mif ! git rev-parse "$MERGE_BASE:.circleci/docker"; then�[0m
2022-03-30T17:52:59.2572159Z �[36;1m  echo "Directory '.circleci/docker' not found in commit $MERGE_BASE, you should probably rebase onto a more recent commit"�[0m
2022-03-30T17:52:59.2572436Z �[36;1m  exit 1�[0m
2022-03-30T17:52:59.2572596Z �[36;1mfi�[0m
2022-03-30T17:52:59.2572815Z �[36;1mPREVIOUS_DOCKER_TAG=$(git rev-parse "$MERGE_BASE:.circleci/docker")�[0m
2022-03-30T17:52:59.2573143Z �[36;1m# If no image exists but the hash is the same as the previous hash then we should error out here�[0m
2022-03-30T17:52:59.2573441Z �[36;1mif [[ "${PREVIOUS_DOCKER_TAG}" = "${DOCKER_TAG}" ]]; then�[0m
2022-03-30T17:52:59.2573769Z �[36;1m  echo "ERROR: Something has gone wrong and the previous image isn't available for the merge-base of your branch"�[0m
2022-03-30T17:52:59.2574095Z �[36;1m  echo "       contact the PyTorch team to restore the original images"�[0m
2022-03-30T17:52:59.2574399Z �[36;1m  exit 1�[0m
2022-03-30T17:52:59.2574561Z �[36;1mfi�[0m
2022-03-30T17:52:59.2574743Z �[36;1mecho ::set-output name=rebuild::yes�[0m
2022-03-30T17:52:59.2585042Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-03-30T17:52:59.2585259Z env:
2022-03-30T17:52:59.2585403Z   IN_CI: 1
2022-03-30T17:52:59.2585559Z   IS_GHA: 1
2022-03-30T17:52:59.2585778Z   BASE_REVISION: dfe6e88adca3969eef148c0fa74795fe2ba2bc9e
2022-03-30T17:52:59.2586187Z   DOCKER_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/pytorch/pytorch-linux-xenial-cuda11.3-cudnn8-py3-gcc7:a2c09c6009bb8a10cbb45a8c5f7c573593289be0

See GitHub Actions build trunk / libtorch-linux-xenial-cuda11.3-py3.7-gcc7 / build (2/5)

Step: "Build" (full log | diagnosis details | 🔁 rerun)

2022-03-30T20:58:11.8598065Z �[36;1m echo "ERR...t available for the merge-base of your branch"�[0m
2022-03-30T20:58:11.8594911Z �[36;1mfi�[0m
2022-03-30T20:58:11.8595138Z �[36;1m# Covers the case where a previous tag doesn't exist for the tree�[0m
2022-03-30T20:58:11.8595479Z �[36;1m# this is only really applicable on trees that don't have `.circleci/docker` at its merge base, i.e. nightly�[0m
2022-03-30T20:58:11.8595788Z �[36;1mif ! git rev-parse "$MERGE_BASE:.circleci/docker"; then�[0m
2022-03-30T20:58:11.8596127Z �[36;1m  echo "Directory '.circleci/docker' not found in commit $MERGE_BASE, you should probably rebase onto a more recent commit"�[0m
2022-03-30T20:58:11.8596405Z �[36;1m  exit 1�[0m
2022-03-30T20:58:11.8596568Z �[36;1mfi�[0m
2022-03-30T20:58:11.8596788Z �[36;1mPREVIOUS_DOCKER_TAG=$(git rev-parse "$MERGE_BASE:.circleci/docker")�[0m
2022-03-30T20:58:11.8597118Z �[36;1m# If no image exists but the hash is the same as the previous hash then we should error out here�[0m
2022-03-30T20:58:11.8597734Z �[36;1mif [[ "${PREVIOUS_DOCKER_TAG}" = "${DOCKER_TAG}" ]]; then�[0m
2022-03-30T20:58:11.8598065Z �[36;1m  echo "ERROR: Something has gone wrong and the previous image isn't available for the merge-base of your branch"�[0m
2022-03-30T20:58:11.8598393Z �[36;1m  echo "       contact the PyTorch team to restore the original images"�[0m
2022-03-30T20:58:11.8598694Z �[36;1m  exit 1�[0m
2022-03-30T20:58:11.8598861Z �[36;1mfi�[0m
2022-03-30T20:58:11.8599043Z �[36;1mecho ::set-output name=rebuild::yes�[0m
2022-03-30T20:58:11.8609617Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-03-30T20:58:11.8609837Z env:
2022-03-30T20:58:11.8609983Z   IN_CI: 1
2022-03-30T20:58:11.8610141Z   IS_GHA: 1
2022-03-30T20:58:11.8610358Z   BASE_REVISION: b633db1f99ec41ca68f8064b95f739e2b983ef2d
2022-03-30T20:58:11.8610761Z   DOCKER_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/pytorch/pytorch-linux-xenial-cuda11.3-cudnn8-py3-gcc7:a2c09c6009bb8a10cbb45a8c5f7c573593289be0

See GitHub Actions build trunk / linux-xenial-cuda11.3-py3.7-gcc7-no-ops / build (3/5)

Step: "Build" (full log | diagnosis details | 🔁 rerun)

2022-03-30T20:58:14.5566709Z �[36;1m echo "ERR...t available for the merge-base of your branch"�[0m
2022-03-30T20:58:14.5563773Z �[36;1mfi�[0m
2022-03-30T20:58:14.5564001Z �[36;1m# Covers the case where a previous tag doesn't exist for the tree�[0m
2022-03-30T20:58:14.5564349Z �[36;1m# this is only really applicable on trees that don't have `.circleci/docker` at its merge base, i.e. nightly�[0m
2022-03-30T20:58:14.5564665Z �[36;1mif ! git rev-parse "$MERGE_BASE:.circleci/docker"; then�[0m
2022-03-30T20:58:14.5565006Z �[36;1m  echo "Directory '.circleci/docker' not found in commit $MERGE_BASE, you should probably rebase onto a more recent commit"�[0m
2022-03-30T20:58:14.5565290Z �[36;1m  exit 1�[0m
2022-03-30T20:58:14.5565459Z �[36;1mfi�[0m
2022-03-30T20:58:14.5565681Z �[36;1mPREVIOUS_DOCKER_TAG=$(git rev-parse "$MERGE_BASE:.circleci/docker")�[0m
2022-03-30T20:58:14.5566071Z �[36;1m# If no image exists but the hash is the same as the previous hash then we should error out here�[0m
2022-03-30T20:58:14.5566375Z �[36;1mif [[ "${PREVIOUS_DOCKER_TAG}" = "${DOCKER_TAG}" ]]; then�[0m
2022-03-30T20:58:14.5566709Z �[36;1m  echo "ERROR: Something has gone wrong and the previous image isn't available for the merge-base of your branch"�[0m
2022-03-30T20:58:14.5567040Z �[36;1m  echo "       contact the PyTorch team to restore the original images"�[0m
2022-03-30T20:58:14.5567336Z �[36;1m  exit 1�[0m
2022-03-30T20:58:14.5567503Z �[36;1mfi�[0m
2022-03-30T20:58:14.5567687Z �[36;1mecho ::set-output name=rebuild::yes�[0m
2022-03-30T20:58:14.5578124Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-03-30T20:58:14.5578343Z env:
2022-03-30T20:58:14.5578489Z   IN_CI: 1
2022-03-30T20:58:14.5578650Z   IS_GHA: 1
2022-03-30T20:58:14.5578868Z   BASE_REVISION: b633db1f99ec41ca68f8064b95f739e2b983ef2d
2022-03-30T20:58:14.5579276Z   DOCKER_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/pytorch/pytorch-linux-xenial-cuda11.3-cudnn8-py3-gcc7:a2c09c6009bb8a10cbb45a8c5f7c573593289be0

See GitHub Actions build pull / deploy-linux-xenial-cuda11.3-py3.7-gcc7 / build (4/5)

Step: "Build" (full log | diagnosis details | 🔁 rerun)

2022-03-30T17:52:54.4178829Z �[36;1m echo "ERR...t available for the merge-base of your branch"�[0m
2022-03-30T17:52:54.4175915Z �[36;1mfi�[0m
2022-03-30T17:52:54.4176185Z �[36;1m# Covers the case where a previous tag doesn't exist for the tree�[0m
2022-03-30T17:52:54.4176538Z �[36;1m# this is only really applicable on trees that don't have `.circleci/docker` at its merge base, i.e. nightly�[0m
2022-03-30T17:52:54.4176866Z �[36;1mif ! git rev-parse "$MERGE_BASE:.circleci/docker"; then�[0m
2022-03-30T17:52:54.4177201Z �[36;1m  echo "Directory '.circleci/docker' not found in commit $MERGE_BASE, you should probably rebase onto a more recent commit"�[0m
2022-03-30T17:52:54.4177483Z �[36;1m  exit 1�[0m
2022-03-30T17:52:54.4177649Z �[36;1mfi�[0m
2022-03-30T17:52:54.4177870Z �[36;1mPREVIOUS_DOCKER_TAG=$(git rev-parse "$MERGE_BASE:.circleci/docker")�[0m
2022-03-30T17:52:54.4178198Z �[36;1m# If no image exists but the hash is the same as the previous hash then we should error out here�[0m
2022-03-30T17:52:54.4178502Z �[36;1mif [[ "${PREVIOUS_DOCKER_TAG}" = "${DOCKER_TAG}" ]]; then�[0m
2022-03-30T17:52:54.4178829Z �[36;1m  echo "ERROR: Something has gone wrong and the previous image isn't available for the merge-base of your branch"�[0m
2022-03-30T17:52:54.4179166Z �[36;1m  echo "       contact the PyTorch team to restore the original images"�[0m
2022-03-30T17:52:54.4179488Z �[36;1m  exit 1�[0m
2022-03-30T17:52:54.4179660Z �[36;1mfi�[0m
2022-03-30T17:52:54.4179848Z �[36;1mecho ::set-output name=rebuild::yes�[0m
2022-03-30T17:52:54.4191275Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-03-30T17:52:54.4191496Z env:
2022-03-30T17:52:54.4191656Z   IN_CI: 1
2022-03-30T17:52:54.4191805Z   IS_GHA: 1
2022-03-30T17:52:54.4192028Z   BASE_REVISION: dfe6e88adca3969eef148c0fa74795fe2ba2bc9e
2022-03-30T17:52:54.4192451Z   DOCKER_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/pytorch/pytorch-linux-xenial-cuda11.3-cudnn8-py3-gcc7:a2c09c6009bb8a10cbb45a8c5f7c573593289be0

See GitHub Actions build pull / linux-xenial-cuda11.3-py3.7-gcc7-bazel-test / build-and-test (5/5)

Step: "Build" (full log | diagnosis details | 🔁 rerun)

2022-03-30T17:53:11.5454729Z �[36;1m echo "ERR...t available for the merge-base of your branch"�[0m
2022-03-30T17:53:11.5451417Z �[36;1mfi�[0m
2022-03-30T17:53:11.5451686Z �[36;1m# Covers the case where a previous tag doesn't exist for the tree�[0m
2022-03-30T17:53:11.5452075Z �[36;1m# this is only really applicable on trees that don't have `.circleci/docker` at its merge base, i.e. nightly�[0m
2022-03-30T17:53:11.5452435Z �[36;1mif ! git rev-parse "$MERGE_BASE:.circleci/docker"; then�[0m
2022-03-30T17:53:11.5452824Z �[36;1m  echo "Directory '.circleci/docker' not found in commit $MERGE_BASE, you should probably rebase onto a more recent commit"�[0m
2022-03-30T17:53:11.5453152Z �[36;1m  exit 1�[0m
2022-03-30T17:53:11.5453357Z �[36;1mfi�[0m
2022-03-30T17:53:11.5453621Z �[36;1mPREVIOUS_DOCKER_TAG=$(git rev-parse "$MERGE_BASE:.circleci/docker")�[0m
2022-03-30T17:53:11.5453999Z �[36;1m# If no image exists but the hash is the same as the previous hash then we should error out here�[0m
2022-03-30T17:53:11.5454349Z �[36;1mif [[ "${PREVIOUS_DOCKER_TAG}" = "${DOCKER_TAG}" ]]; then�[0m
2022-03-30T17:53:11.5454729Z �[36;1m  echo "ERROR: Something has gone wrong and the previous image isn't available for the merge-base of your branch"�[0m
2022-03-30T17:53:11.5455174Z �[36;1m  echo "       contact the PyTorch team to restore the original images"�[0m
2022-03-30T17:53:11.5455452Z �[36;1m  exit 1�[0m
2022-03-30T17:53:11.5455656Z �[36;1mfi�[0m
2022-03-30T17:53:11.5455881Z �[36;1mecho ::set-output name=rebuild::yes�[0m
2022-03-30T17:53:11.5466235Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-03-30T17:53:11.5466490Z env:
2022-03-30T17:53:11.5466674Z   IN_CI: 1
2022-03-30T17:53:11.5466872Z   IS_GHA: 1
2022-03-30T17:53:11.5467097Z   GIT_DEFAULT_BRANCH: master
2022-03-30T17:53:11.5467370Z   BASE_REVISION: dfe6e88adca3969eef148c0fa74795fe2ba2bc9e

1 failure not recognized by patterns:

Job Step Action
GitHub Actions pull / pytorch-xla-linux-bionic-py3.7-clang8 / test (xla, 1, 1, linux.2xlarge) Test 🔁 rerun

🚧 1 fixed upstream failure:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@linbinyu linbinyu requested a review from kit1980 March 30, 2022 07:07
@linbinyu
Copy link
Copy Markdown
Contributor Author

@pytorchmergebot merge this

@linbinyu linbinyu added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 30, 2022
@github-actions
Copy link
Copy Markdown
Contributor

Hey @linbinyu.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Mar 31, 2022
Summary:
See #74793 for more details
Redo everything in one pr. This diff added test model generation script and updated android and ios tests.

Pull Request resolved: #74947
Approved by: https://github.com/kit1980

allow-large-files

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/28a4b4759add0b3eb0f4c34a1e042be4f93e976e

Reviewed By: atalman

Differential Revision: D35284140

Pulled By: linbinyu

fbshipit-source-id: 50c73e006554b8e4301275599433b69950ff9e33
@github-actions github-actions Bot deleted the linbin/test_models branch February 15, 2024 01:56
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 25, 2026
See pytorch#74793 for more details
Redo everything in one pr. This diff added test model generation script and updated android and ios tests.
Pull Request resolved: pytorch#74947
Approved by: https://github.com/kit1980
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request cla signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants