Expensive failed runs with no error messages

[aaronadamsCA]

This action caused our CI pipeline to hit its billing limits because it started failing, with each failure using 6 hours (!) of billable time while logging no useful information to help debug.

The relevant part of the raw logs:

2022-03-19T18:27:27.4081768Z ##[group]Run Azure/functions-action@v1
2022-03-19T18:27:27.4082022Z with:
2022-03-19T18:27:27.4082267Z   app-name: ***
2022-03-19T18:27:27.4082518Z   package: deploy
2022-03-19T18:27:27.4082745Z   slot-name: staging
2022-03-19T18:27:27.4086015Z   publish-profile: ***
2022-03-19T18:27:27.4086269Z   respect-pom-xml: false
2022-03-19T18:27:27.4086524Z   respect-funcignore: false
2022-03-19T18:27:27.4086817Z   scm-do-build-during-deployment: false
2022-03-19T18:27:27.4087099Z   enable-oryx-build: false
...
2022-03-19T18:27:27.4094955Z ##[endgroup]
2022-03-19T18:27:27.6729423Z Successfully parsed SCM credential from old publish-profile format.
2022-03-19T18:27:27.6740949Z Using SCM credential for authentication, GitHub Action will not perform resource validation.
2022-03-20T00:26:14.2959392Z ##[error]The operation was canceled.

Since we're fleeing Azure for greener pastures, I've simply disabled all builds.

I think this might have happened because the action was trying to deploy using a publish profile that was no longer valid. Still no reason for the action to simply hang.

[patelchandni]

@aaronadamsCA was this a one-time occurrence or is it frequent? Unable to recreate it with expired publish profile as the action exits elegantly.

[github-actions[bot]]

This issue is idle because it has been open for 14 days with no activity.

[patelchandni]

@aaronadamsCA a PR was merged and released which should fixed this issue. Let us know if the issue is still existing.