https://linen.dev logo
Join Slack
Powered by
I'm seeing issues with GHA checks not showing up i...
# report-bugs
j
I'm seeing issues with GHA checks not showing up in graphite after succeeding in github
✅ 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>
j
seems like a live regression / bug
everything is fine in github
but blocked on graphite
no matter how much I try to Cancel all jobs, rerun failed or all jobs etc
unable to merge my PR rn....
p
hey jan, did you make any changes to the stack? i'm currently seeing that ci was triggered again
j
After being blocked by this for 1h, the only way to unblock it now was to go to the Github "All Workflows" UI, filter by my branch, and delete every workflow run associated with this branch. Plus I closed the PR, waited 5 minutes, and reopened
it still seems kind of stuck though
for example seeing this Wiz Security scan which Github isn't showing
github looks fine
p
thanks for the screenshots. i'll take a look into our logs and see if there's anything i can find
j
thank you!
oh okay one update - this was actually happening on two branches / PRs. The one linked above is fine now, after deleting all workflow runs as described. The only one that's still stuck is this one: https://app.graphite.com/github/pr/Rogo-Technologies/ask-rogo/28198
I will attempt deleting all workflow runs, and closing /re-opening that one too
ah yes, closing / reopening the PR seems to have refreshed some state in graphite
I believe we're good now
Would really love for you guys to take a look though. This blocked me for more than one hour
👍 1
p
hey jan, after some digging. it looks like the issue was that github's workflow runner never cleaned up and left some checks in a 
queued
state after new pushes triggered replacement runs. do you currently have Github concurrency configuration set up?
j
yeah we do have that set up correctly
it's weird bc everything also looked fine in github - the checks ran through successfully, but that was just not reflected in graphite
p
yeah i agree with that sentiment. it looks like our team is looking into this issue and i've added your feedback onto the ticket.
j
👍 thank you!
2 Views
Open in Slack
PreviousNext
Powered by