Pedro Goncalves Mokarzel

I initially created https://github.com/pytorch/xla/issues/9334 and https://github.com/pytorch/xla/issues/9356 with the intent to achieve what this bug is talking of doing with `torch_xla::OpSharding`. The idea with those two is to standardize sharding abstractions...

I think this is a nice expansion of https://github.com/pytorch/xla/issues/9357. Marking it as a duplicate of this one.

@rpsilva-aws From the RFC, this is more to demonstrate how pipeline parallelism can be achieved through different libraries. Both Ray and PiPPy are valid cases that customers can seek. To...

I have drilled down further here. The torchprime test errors seem to be coming from trying to build a version of pytorch that does not exist `torch-2.9.0-cp312-cp312-linux_x86_64.whl` from its dockerfile...

https://github.com/pytorch/xla/issues/9466#issuecomment-3074640270 was going down the wrong rabbit hole. The issue actually seems to be tied to updating to PyTorch 3.12. Latest commit to on https://github.com/pytorch/xla/pull/9481 ([commit link](https://github.com/pytorch/xla/pull/9481/commits/04f48f1446d61a14a2d7f4c52d77356a5ed25e7e)) tested that theory,...

Once resolved, we have been asked to close https://github.com/pytorch/pytorch/issues/158876

Other tests seem to be effected: https://github.com/pytorch/pytorch/actions/runs/16457516513/job/46518864660

I believe the issue has been resolved in https://github.com/pytorch/xla/pull/9565. Based on recent runs, that seems to be true from the [pytorch more recent test runs](https://github.com/pytorch/pytorch/actions/workflows/lint.yml): - https://github.com/pytorch/pytorch/actions/runs/17406954070 - https://github.com/pytorch/pytorch/actions/runs/17406351178

@ZainRizvi Please let me know if this is still impacting tests

LGTM pending tests