Azure Devops cscript error - Unexpected end of JSON input
Multi tool use
up vote
1
down vote
favorite
I'm currently setting up an automated UI-test pipeline for a client. The pipeline itself is working (Selenium tests are running and ending accordingly), but at the start of the vstest task, the following error shows in the release:
The log itself is only slightly more informative:
2018-11-08T09:01:27.5866296Z VisualStudio version selected for test execution : latest
2018-11-08T09:01:27.7436467Z ========================================================
2018-11-08T09:01:27.7481019Z ======================================================
2018-11-08T09:01:27.7896471Z [command]"C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe" @C:vstsagentA3_work_tempe063c6c1-e334-11e8-96ca-cb244534022f.txt
2018-11-08T09:01:27.9515408Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:27.9524437Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.0079953Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:28.0095401Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.1547295Z Microsoft (R) Test Execution Command Line Tool Version 15.8.0
2018-11-08T09:01:28.1550589Z Copyright (c) Microsoft Corporation. All rights reserved.
2018-11-08T09:01:28.1550786Z
2018-11-08T09:01:28.1581289Z vstest.console.exe
The release itself keeps showing as "partially succeeded", which badly influences the automatic notifications, as the tests themselves are succeeding without problems. So far I haven't been able to find a solution in this context.
Does anyone have an idea of how to fix this? I'll be happy to provide more info if needed.
json
azure-devops azure-pipelines-release-pipeline vstest.console.exe asked Nov 8 at 9:56
Tybs
15513
add a comment |
up vote
1
down vote
favorite
I'm currently setting up an automated UI-test pipeline for a client. The pipeline itself is working (Selenium tests are running and ending accordingly), but at the start of the vstest task, the following error shows in the release:
The log itself is only slightly more informative:
2018-11-08T09:01:27.5866296Z VisualStudio version selected for test execution : latest
2018-11-08T09:01:27.7436467Z ========================================================
2018-11-08T09:01:27.7481019Z ======================================================
2018-11-08T09:01:27.7896471Z [command]"C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe" @C:vstsagentA3_work_tempe063c6c1-e334-11e8-96ca-cb244534022f.txt
2018-11-08T09:01:27.9515408Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:27.9524437Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.0079953Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:28.0095401Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.1547295Z Microsoft (R) Test Execution Command Line Tool Version 15.8.0
2018-11-08T09:01:28.1550589Z Copyright (c) Microsoft Corporation. All rights reserved.
2018-11-08T09:01:28.1550786Z
2018-11-08T09:01:28.1581289Z vstest.console.exe
The release itself keeps showing as "partially succeeded", which badly influences the automatic notifications, as the tests themselves are succeeding without problems. So far I haven't been able to find a solution in this context.
Does anyone have an idea of how to fix this? I'll be happy to provide more info if needed.
json
azure-devops azure-pipelines-release-pipeline vstest.console.exe asked Nov 8 at 9:56
Tybs
15513
Can you run the same release withsystem.debug=trueand share the logs?
– Shayki Abramczyk
Nov 8 at 11:45
We just fixed the issue, as mentioned in the given answer. Still, thanks for the advice!
– Tybs
Nov 8 at 14:49
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm currently setting up an automated UI-test pipeline for a client. The pipeline itself is working (Selenium tests are running and ending accordingly), but at the start of the vstest task, the following error shows in the release:
The log itself is only slightly more informative:
2018-11-08T09:01:27.5866296Z VisualStudio version selected for test execution : latest
2018-11-08T09:01:27.7436467Z ========================================================
2018-11-08T09:01:27.7481019Z ======================================================
2018-11-08T09:01:27.7896471Z [command]"C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe" @C:vstsagentA3_work_tempe063c6c1-e334-11e8-96ca-cb244534022f.txt
2018-11-08T09:01:27.9515408Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:27.9524437Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.0079953Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:28.0095401Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.1547295Z Microsoft (R) Test Execution Command Line Tool Version 15.8.0
2018-11-08T09:01:28.1550589Z Copyright (c) Microsoft Corporation. All rights reserved.
2018-11-08T09:01:28.1550786Z
2018-11-08T09:01:28.1581289Z vstest.console.exe
The release itself keeps showing as "partially succeeded", which badly influences the automatic notifications, as the tests themselves are succeeding without problems. So far I haven't been able to find a solution in this context.
Does anyone have an idea of how to fix this? I'll be happy to provide more info if needed.
json
azure-devops azure-pipelines-release-pipeline vstest.console.exe asked Nov 8 at 9:56
Tybs
15513
I'm currently setting up an automated UI-test pipeline for a client. The pipeline itself is working (Selenium tests are running and ending accordingly), but at the start of the vstest task, the following error shows in the release:
The log itself is only slightly more informative:
2018-11-08T09:01:27.5866296Z VisualStudio version selected for test execution : latest
2018-11-08T09:01:27.7436467Z ========================================================
2018-11-08T09:01:27.7481019Z ======================================================
2018-11-08T09:01:27.7896471Z [command]"C:Program Files (x86)Microsoft Visual Studio2017ProfessionalCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe" @C:vstsagentA3_work_tempe063c6c1-e334-11e8-96ca-cb244534022f.txt
2018-11-08T09:01:27.9515408Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:27.9524437Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.0079953Z ##[error]Unhandled: Unexpected end of JSON input
2018-11-08T09:01:28.0095401Z ##[error]Unhandled: Command failed: cscript.exe //Nologo C:vstsagentA3_work_tasksVSTest_ef087383-ee5e-42c7-9a53-ab56c98420f92.142.12node_modulesregeditvbsregListStream.wsf A
2018-11-08T09:01:28.1547295Z Microsoft (R) Test Execution Command Line Tool Version 15.8.0
2018-11-08T09:01:28.1550589Z Copyright (c) Microsoft Corporation. All rights reserved.
2018-11-08T09:01:28.1550786Z
2018-11-08T09:01:28.1581289Z vstest.console.exe
The release itself keeps showing as "partially succeeded", which badly influences the automatic notifications, as the tests themselves are succeeding without problems. So far I haven't been able to find a solution in this context.
Does anyone have an idea of how to fix this? I'll be happy to provide more info if needed.
json
azure-devops azure-pipelines-release-pipeline vstest.console.exe json
azure-devops azure-pipelines-release-pipeline vstest.console.exe asked Nov 8 at 9:56
Tybs
15513
asked Nov 8 at 9:56
Tybs
15513
edited Nov 8 at 10:03
asked Nov 8 at 9:56
Tybs
15513
asked Nov 8 at 9:56
Tybs
15513
asked Nov 8 at 9:56
Tybs
15513
15513
Can you run the same release withsystem.debug=trueand share the logs?
– Shayki Abramczyk
Nov 8 at 11:45
We just fixed the issue, as mentioned in the given answer. Still, thanks for the advice!
– Tybs
Nov 8 at 14:49
add a comment |
Can you run the same release withsystem.debug=trueand share the logs?
– Shayki Abramczyk
Nov 8 at 11:45
We just fixed the issue, as mentioned in the given answer. Still, thanks for the advice!
– Tybs
Nov 8 at 14:49
Can you run the same release with
system.debug=true and share the logs?– Shayki Abramczyk
Nov 8 at 11:45
Can you run the same release with
system.debug=true and share the logs?– Shayki Abramczyk
Nov 8 at 11:45
We just fixed the issue, as mentioned in the given answer. Still, thanks for the advice!
– Tybs
Nov 8 at 14:49
We just fixed the issue, as mentioned in the given answer. Still, thanks for the advice!
– Tybs
Nov 8 at 14:49
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
We just managed to get rid of the errors by re-adding the build agent in the old way (heading to _settings/agentqueues "Agent Pools" and using "Download Agent").
Previously, we configured the agent using Deployment Groups: though I still don't know why, this apparently had something to do with the issue.
answered Nov 8 at 14:48
Tybs
15513
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
We just managed to get rid of the errors by re-adding the build agent in the old way (heading to _settings/agentqueues "Agent Pools" and using "Download Agent").
Previously, we configured the agent using Deployment Groups: though I still don't know why, this apparently had something to do with the issue.
answered Nov 8 at 14:48
Tybs
15513
add a comment |
up vote
0
down vote
accepted
We just managed to get rid of the errors by re-adding the build agent in the old way (heading to _settings/agentqueues "Agent Pools" and using "Download Agent").
Previously, we configured the agent using Deployment Groups: though I still don't know why, this apparently had something to do with the issue.
answered Nov 8 at 14:48
Tybs
15513
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
We just managed to get rid of the errors by re-adding the build agent in the old way (heading to _settings/agentqueues "Agent Pools" and using "Download Agent").
Previously, we configured the agent using Deployment Groups: though I still don't know why, this apparently had something to do with the issue.
answered Nov 8 at 14:48
Tybs
15513
We just managed to get rid of the errors by re-adding the build agent in the old way (heading to _settings/agentqueues "Agent Pools" and using "Download Agent").
Previously, we configured the agent using Deployment Groups: though I still don't know why, this apparently had something to do with the issue.
answered Nov 8 at 14:48
Tybs
15513
answered Nov 8 at 14:48
Tybs
15513
answered Nov 8 at 14:48
Tybs
15513
answered Nov 8 at 14:48
Tybs
15513
15513
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53205281%2fazure-devops-cscript-error-unexpected-end-of-json-input%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
mBU4if,dkGBhnAJx,5d9KzbAqQh2S4ziR,c05sTM8j8nb7tfbbAzSDZCX,NM9NMUodZ5VdKk2
Can you run the same release with
system.debug=trueand share the logs?– Shayki Abramczyk
Nov 8 at 11:45
We just fixed the issue, as mentioned in the given answer. Still, thanks for the advice!
– Tybs
Nov 8 at 14:49