Skip to content

[Bug] Azure Execute hangs for ~25 minutes and then fails with generic node error. #2864

@scphantm

Description

@scphantm

Describe the bug
i reported this here GitTools/actions#511 but havn't gotten any response, my logs and such are over there.

Heres the basic, when we are seeding a repo, the azure pipeline will hang on the GitVersion Execute task. we don't know why, but when it does happen, it will hang for about 30 minutes and then fail with a generic node error. What fixes it is simply creating a new PR with just a white space commit to it.

the bug is 2 fold

1 - why is it failing
2 - why is it failing in such a way that we can't debug.

Expected Behavior

It works

Actual Behavior

It hangs on the execute task until Node or Azure times out.

Possible Fix

putting in a white space commit makes it work again.

Steps to Reproduce

when we are seeding our repos, the initial commits cause the thing to hang. Simply adding a blank white space commit will clear the error.

Context

we have hundreds of repos and pipelines. This is killing us.

Your Environment

Azure Pipelines

  • Version Used:
  • Operating System and version (Windows 10, Ubuntu 18.04):
  • Link to your project:
  • Link to your CI build (if appropriate):

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions