Debugging Workflow
Stay organized with collections
Save and categorize content based on your preferences.
This document describe a general workflow for debugging MXLA issues.
Prerequisite
Use JAX 0.6 or up, and enable JAX distributed service. This version of JAX
contains additional logging that can help identify which workers are
experiencing issues.
Generate an HLO dump using the --xla_dump_to flag when initializing your
workload. This is discussed in the XLA
documentation.
Set --vmodule=real_program_continuator=1 to enable verbose logging for the
TPU program execution status.
Flow chart
The flowchart below illustrates the debugging process. To access detailed
playbooks for each step, click on the corresponding item in the chart.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-03-02 UTC."],[],[]]
