Huy Do

@pytorchbot rebase -s

@pytorchbot revert -m 'This breaks CUDA 10.2 in trunk. We are deprecating CUDA 10.2, but it is still here in the mean time' -c nosignal

Could we just remove the `appy_patches` functionality from PyTorch XLA test?

cc @JackCaoG @rdspring1 I see you guys last touched this file https://github.com/pytorch/xla/blob/master/scripts/apply_patches.sh a while ago, do you think if this could be removed or fixed somehow?

The direct cause is that after the commit message `Pull Request resolved: https://github.com/pytorch/pytorch/pull/73164` disappears from the list of last 100 commits. PyTorch will be built using #73164 head instead and...

I'll rebase this on top of https://github.com/pytorch/pytorch/pull/92193 once the latter is merged

@pytorchbot merge

@pytorchbot revert -m 'This breaks inductor_distributed workflow https://hud.pytorch.org/pytorch/pytorch/commit/a383789f4d8ecb36adaff6bd3746430209ff0546' -c nosignal

I think the cherry pick bot fails on this PR because it wasn't merged properly by the bot, i.e. https://github.com/pytorch/executorch/pull/3260#issuecomment-2073792645. Here is the corresponding log https://github.com/pytorch/executorch/actions/runs/8822987799/job/24222413111, so I think this...

Just FYI, if you want the authentication with AWS on `Android / test-llama-app / mobile-job` to pass, choose not to use a forked PR when exporting the PR. Only ET...