Workflow never completes

[markdthompson-SR]

The action deployed to Heroku successfully, but hangs on the 'Run akhileshns/[email protected]' step, and never finishes:

Here's my main.yml with app-name & email removed:

name: Deploy

on:
  push:
    branches:
      - master

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: akhileshns/[email protected] # This is the action
        with:
          heroku_api_key: ${{secrets.HEROKU_API_KEY}}
          heroku_app_name: "YOUR APP's NAME" #Must be unique in Heroku
          heroku_email: "YOUR EMAIL"`

---

[markdthompson-SR]

Also note that the action did not respond to cancelling the action:

[ferny1313]

Sometimes GitHub Actions take to much to run my tests, but it seems to be something random. 🤔
They also have a problem with cache, did you refresh the page? 😅

[markdthompson-SR]

Thanks for the quick response Fernando. Yeah, I did refresh, didn't seem to have an effect. Ultimately, after about 1/2 hr I cancelled the action - the deploy to Heroku had long since completed. Also, the triangle next to the step that hangs never appears, so unfortunately I can give you any info on exceptions, etc

…

On Fri, Apr 29, 2022 at 1:48 AM Fernando Alberto Gonzalez Rascon < ***@***.***> wrote: Sometimes GitHub Actions take to much to run my tests, but it seems to be something random. 🤔 They also have a problem with cache, did you refresh the page? 😅 — Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP4MEGLM4TJIKUACEK4LXD3VHNZ35ANCNFSM5UTAGHSA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- MARK D THOMPSON Square Roots▪Senior Infrastructure Engineer — squarerootsgrow.com <http://www.squarerootsgrow.com/> Instagram <https://www.instagram.com/squarerootsgrow/?hl=en>▪Facebook <https://www.facebook.com/squarerootsgrow/>▪Twitter <https://twitter.com/squarerootsgrow?lang=en> Store Locator <https://www.squarerootsgrow.com/store-locator> — Fresh, locally grown greens, all year round.

[kimmy-wang]

same issue

[kimmy-wang]

[markdthompson-SR]

Hi Fernando - a little more info on this issue. Id did get some feedback from the Run action step, here's a screenshot attached. Looks like a lot of output (same output as Heroku log for the deploy?). Seems to stop at line 505, even though in the Heroku log, there is quite a bit more output. The action output gets written after the Heroku deploy completes. I'm wondering if maybe there's an output buffer limit that's being exceeded?

…

On Fri, Apr 29, 2022 at 1:48 AM Fernando Alberto Gonzalez Rascon < ***@***.***> wrote: Sometimes GitHub Actions take to much to run my tests, but it seems to be something random. 🤔 They also have a problem with cache, did you refresh the page? 😅 — Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP4MEGLM4TJIKUACEK4LXD3VHNZ35ANCNFSM5UTAGHSA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- MARK D THOMPSON Square Roots▪Senior Infrastructure Engineer — squarerootsgrow.com <http://www.squarerootsgrow.com/> Instagram <https://www.instagram.com/squarerootsgrow/?hl=en>▪Facebook <https://www.facebook.com/squarerootsgrow/>▪Twitter <https://twitter.com/squarerootsgrow?lang=en> Store Locator <https://www.squarerootsgrow.com/store-locator> — Fresh, locally grown greens, all year round.

[Fabien-R]

We also have this kind of behavior. But I don't think it's a problem coming from this github action.

What we saw :

• All stuck deployments had their building step in heroku dashboard never finished. Or stopped by Heroku team, 2h later. But they never finished.
• There was not explicit errors about this timeout. Log in Heroku building console was stuck.
• We did not saw pb for building step taking less than 14 minutes
• Reading some doc we saw there was mention about a 15 minutes limits.
  --> the first problem was that even in Heroku dashboard all the timeouts was silent and waiting for more than 15 minutes without any error is not great
  --> the second problem is the consumption of Github credit. Having several deployments taking 1h and that will eventually failed is not good for our finances.

So a workaround for us was at github action level to timeout the step:

deployment:
    runs-on: ubuntu-latest
    timeout-minutes: 14
    steps:
      - uses: actions/checkout@v3
      - uses: akhileshns/[email protected]

It won't solve Heroku problem, but it will save your time and credit. To relaunch another workflow quicker.

Hope this can help