search

linear-b / gitstream

/:\ gitStream - Workflow automation for your git repo. Use YAML to auto-assign reviewers, auto-merge PRs, automatic PR labeler, and more.
https://gitstream.cm
Apache License 2.0
272 stars 33 forks source link

gitStream check is failing - The job running on runner Hosted Agent has exceeded the maximum execution time of 5 minutes. #10

Closed AnkurAgarwal-ST closed 1 year ago

AnkurAgarwal-ST commented 1 year ago

Describe the bug

In one of the PR, gitStream seems to be stuck. We tried even with multiple commits so that the check could restart, but there was still no success & it remains in "In progress — This check has started...." state PR URL - https://github.com/Hodes-Inc/XCloud.JEE6.CoreAPIs/pull/7201

To Reproduce

Steps to reproduce the behavior: Raise a PR and wait for the gitstream checks to finish. Notice that the gitStream status is shown as "In progress for hours" in the pr, but if we check inside Actions list of the repo it will shown as failed. The actions displays the error as - "The job running on runner Hosted Agent has exceeded the maximum execution time of 5 minutes."

Expected behavior

The gitstream should not be failed with message "The job running on runner Hosted Agent has exceeded the maximum execution time of 5 minutes." The gitStream checks should be executed and get finished in a reasonable time. If the gitstream check has failed, it should be reflected in the PR status check sections as well.

Screenshots

image image image

Additional context

This issue has been noticed for this one particular pr only.

vim-zz commented 1 year ago

We are looking at it @AnkurAgarwal-ST

vim-zz commented 1 year ago

@AnkurAgarwal-ST we found the issue, it happens because you manually removed a label that was genereted automatically and this got the action get to an undefined behavior. The issue was fixed, please do another commit to the PR to get it back to normal state.

AnkurAgarwal-ST commented 1 year ago

Hi @vim-zz, I don't think anyone removed a label auto-generated by gitStream. gitStream has never been able to run once on the reported pr, so it cannot generate any label. I also checked the activity on the pr and I can't find any action of adding or removing label either by a team member or by gitstream. We have merged that pr now so we cannot test anymore on that pr.

Please correct me if I am missing something.

vim-zz commented 1 year ago

We identifed a state that results with undefined behavior when handling some scenarios so fixing that should cover this kind of issues. I will close this bug and if you encounter this kind of issue again please re-open it or open a new issue.