Hi all. Not sure if I have hit a bug or another i...
# report-bugs
m
Hi all. Not sure if I have hit a bug or another issue. When my stacks try to merge they sit there for hours get evicted and never get processed. Im using CI optimization. This is reproducible and happens with every stack
✅ 1
p
(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>
hey marc, can you send the PR link so i can take a look?
m
It's a private repo
p
thanks! i'll take a look and get back to you after my investigation
👍 1
m
That's the first eviction. I kicked it and it's now at https://app.graphite.com/github/pr/pokeys-toolkit/simPlex/529/fix(ui)-keep-splash-open-until-React-paints-first-frame which will also evict in about an hour
p
Looking at the failed run vs successful run for https://app.graphite.com/github/pr/pokeys-toolkit/simPlex/528 as an example (part of the draft you shared).. seems like we failed the merge attempt 3 times with the last (4/10/2026, 82249 AM) being on account of a number of tests failing (format, clippy, unit test, and GUI typecheck) whereas the success (4/10/2026, 100329 AM) these tests passed as did the 2 what i thnk are rollups (PR Status and Merge Status). Any idea why these would have failed? Im not sure the CI Optimzations would impact here, they should be returning true on these draft PRs and we would see skipped not failed if otherwise. I think these should be the run IDs of the failure that might help identify why the checks failed: runs/70781122865 runs/70781122816 runs/70781122858 Let me know if this helps your understanding / if you have further questions-
m
Thanks. I think this is correct. I'm more concerned that it look hours for the process to happen. Are you able to see if the timestamps in your logs indicate a normal duration (excluding) our tests
p
hey marc, our logs indicate a normal duration except for the failures. the completed merge only took a few seconds to complete and pass.