Auto-Deployment from VSTS Fails Even When Build Succeeds

#### Investigative information

Please provide the following:

- Timestamp: 11:33 AM 2/23/2018
- Function App version (1.0 or 2.0-beta): (Not Sure)
- Deployment ID: a838656e5c4386c8bbda046f07786b5696ef6dee
- Function name(s) (as appropriate): N/A

Standard Deploy Script Output
```
Command: "D:\home\site\deployments\tools\deploy.cmd"
Handling function App deployment.
Not using funcpack because SCM_USE_FUNCPACK is not set to 1
Installing function extensions from nuget
KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
Copying file: 'azure.deps.js'
Restoring npm packages in "D:\home\site\wwwroot"
Finished successfully.
```
- Region: South Central US

#### Expected behavior

Build is marked as succeeding, since it worked.

#### Actual behavior

Build says it failed, but the output and the application shows that it works.

#### Known workarounds

Since the FuncApp works this behavior is not a huge deal. I've just noticed it for a few weeks and I thought it worth reporting.

#### Related information
* JavaScript

Start with deployment ID a838656e5c4386c8bbda046f07786b5696ef6dee and the D:\home\site\deployments\tools\deploy.cmd output, comparing the reported failure with the successful deployment steps. Done means a successful Azure Functions deployment is reported as a successful build, with the existing application behavior preserved.

Written by the indexing model from the issue text.