Arm backend: Fix bug in ConvertExpandCopyToRepeatPass

[Aleksei-grovety]

In the ConvertExpandCopyToRepeatPass the arguments for the repeat operation are formed incorrectly. For the torch.Tensor.expand operation passing -1 as the size for a dimension means that the size of that dimension does not change. For the DeiT-tiny case, torch.ones(1, 1, 192).expand(1, -1, -1) the pass will prepare arguments to the repeat operation as [1, -1, 1] which will cause an error, in this case the arguments should be [1, 1, 1].

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/7199

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 4 New Failures

As of commit 4d8a7e4 with merge base 62d2e37 ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  RuntimeError: Command docker exec -t aeb5689a502619ca223d540512df6a429c733c9a032188c442e50652733ba500 /exec failed with exit code 2
• pull / unittest-arm / linux-job (gh)
  RuntimeError: Command docker exec -t 0af24547092c3574cf92bd49ce409db3714cc4f6d5f0bb36143422e3e6a835bf /exec failed with exit code 1
• trunk / test-arm-backend-delegation / linux-job (gh)
  RuntimeError: Command docker exec -t 461c4a0f84d90f84efb25ff4b8bc24fea75bd0420cca2b324d3165d7bd33a1fb /exec failed with exit code 1
• trunk / test-arm-reference-delegation / linux-job (gh)
  RuntimeError: Command docker exec -t 32154e10dc0d1bb15f51d967196cc0ab3deecd3eeb30ec0fec2189f0cedf7eea /exec failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

Hi @Aleksei-grovety!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[pytorch-bot]

Please seek CI approval before scheduling CIFlow labels

[freddan80]

Hi @Aleksei-grovety ! This needs a rebase pls

[Aleksei-grovety]

Hi @Aleksei-grovety ! This needs a rebase pls

Hi! Thanks for the advice. Done.

[freddan80]

Thx @Aleksei-grovety! There seem to be a general issue in the CI. See #7285 (comment)
Working on it...

[freddan80]

There's two issues. 1) that you saw in your last log had to do with docker images being push ahead of PR merge. That should be resolved now. 2) this: #7285 (comment)

[freddan80]

@Aleksei-grovety sorry, you need to rebase again for the tests to pass :/