Why does merging stacks take so long
# report-bugsm
Mathew Iacone
10/22/2025, 8:39 PMWhy does merging stacks take so long
p
Pylon
10/22/2025, 8:39 PM(If applicable) To help us repro, please send the following if you haven't already:
- PR links, screenshots, and/or debug output if applicable
- Repro steps
- Does this happen consistently? Just to you or others on your team also?
- Is this a regression? Is the problem new?
- If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>Pylon
10/22/2025, 8:43 PMhey Mathew, that depends on several factors. For the time duration on Graphite's end that includes the size of the stack, the time re-running CI takes after a downstack PR merges and the time Graphite's stack jobs take to process. For the time duration external to Graphite, this will include latency from the network transactions and GitHub's API.
Typically it can be expected to take a few minutes per PR when merging from Graphite. We have more details about what's happening under the hood of the merge process and jobs here.
m
Mathew Iacone
10/22/2025, 8:47 PMHow can i see whats happening in real time? I have no CI right now. Feels like ti should be a lot faster
p
Pylon
10/22/2025, 9:41 PMthere isn't a way to see all these underlying process in the UI in realt-ime. A PR's Activity log (keyboard shortcut
3m
Mathew Iacone
10/23/2025, 2:32 PMIs 10 mins for a ~5 PR stack normal?
p
Pylon
10/23/2025, 2:33 PMYes, 1-2 minutes per PR is within expected duration
m
Mathew Iacone
10/23/2025, 2:35 PMok
Mathew Iacone
10/23/2025, 2:35 PMwould love if that was faster