PyTorch adds a flight recorder to diagnose GPU training job hangs

The new release promotes a fault-focused communications backend and a diagnostic flight recorder so one bad GPU no longer sinks an entire run One faulty GPU used to be able to take down an entire AI training job. With PyTorch 2.15, that single point of failure may stop meaning a full restart. The release, which landed on October 28, 2026, makes a rewritten backend for Nvidia’s Collective Communications Library (NCCL) the default for distributed training. Its job is to help engineers figure out what broke when GPUs work in concert, and to recover without throwing away hours of progress. What changed in PyTorch 2.15 When a model trains across many GPUs, those chips constantly swap data so they stay in sync. NCCL is the library that handles that chatter. The operations it runs are called “collectives,” because every participating GPU has to show up and take part. The rewritten backend is now the default for every nccl process group in PyTorch. A process group is simply the set of GPUs that coordinate on a given task, so the change touches essentially all distributed NCCL training on the framework. This isn’t the backend’s first appearance. It debuted in PyTorch 2.14 as an opt-in featu...