-
Notifications
You must be signed in to change notification settings - Fork 655
Git deploy fails with "Thread was aborted" errors. #2499
Comments
Hello: I tried to push your github repo to a simple web app, and I got:
is this what you are seeing? |
No I've not seen that error before! Apologies, I'd disconnected the git repo deployment so I could just push manually from VS2017. I'm using this as a proof of concept before I make huge changes to a live app, but I'm done changing it now! So to configure deployment from github I just go to the deployment options tab, and select my github account and repository and leave it to do it's thing. We're using this method on numerous other core apps, just not with angular. I've just kicked off a new github deploy, I suspect it will fail again, and then there should be some deployment logs. The only error I've seen is "Thread has been aborted". I tried fixing this by setting the SCM command timeout to 5 mins as suggested by someone else at this issue: #2089 but it doesn't seem to have any effect. |
It's now failed, but with a different error that I've not seen before:
Can't see why it should be running out of memory, it's only a tiny sample application! |
The The original error might be a typescript issue: microsoft/TypeScript#16234 |
That's why I haven't seen that error before then as I'm on an S1 instance. Is there a way of telling if this is due to the syncfusion packages we're re using? It seemed to start failing after adding them, and even now I have to take off the -prod from the angular build or the local publish fails as well! |
Removing -prod flag from the angular build step seems to have fixed it. I'll have to go through the tsconfig options as suggested in the issue linked above and see if I can fix it up. |
One thing that may help is to isolate the step that's failing by running it manually via Kudu console instead of as part of git deployment. See this page. |
We are currently seeing this issue with https://sim-cms-public-staging.azurewebsites.net/ After build is complete, the log message lists this same message twice: Thread was being aborted. |
Also getting this issue with angular build. Was a solution found? |
Also we are getting this when kudu deployment try to install function extensions from nuget. Trace log :
|
@smathangi is your webapp name "payment...box"? If so, it seems like the abort happened because site appSettings was being updated while doing deployment. The update appSettings caused the site to restart. Try to do them in sequence. internal ref: ln1-013. |
@suwatch you're right. Tried them in sequence - no more errors. Thanks much! |
awesome. issue is closed then. |
Hi,
Publishing to azure from visual studio is working fine, and the app builds and runs locally. However, when configuring azure to deploy from my github repo it takes around 20-30 mins before the deployment shows as failed, sometimes with "Thread was aborted" errors, others with no error message at all.
Github repo with the sample solution: https://github.com/sturatcliffe/ng4test
I have had git deploys working earlier this morning, but since then I've added some syncfusion controls to the page, and been trying to tweak the csproj file to only run "npm install" and "npm install -g @angular/cli" when publishing, to prevent it running these scripts everytime we build the app locally.
The app service this is running on is: http://ng-four-test.azurewebsites.net/
Any clues on why the git deploys are failing?
Thanks
The text was updated successfully, but these errors were encountered: