Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PublishTestResults@2 version 2.170.0 fails to upload tasks due to missing PTR_TEST_RUNSUMMARY.json file

See original GitHub issue

Question, Bug, or Feature?
Bug

Enter Task Name: PublishTestResults@2

Environment

Server - Azure Pipelines
- If using Azure Pipelines, provide the account name, team project name, build definition name/build number: Account: MQAutomate Team Project Name: MOSAIQLab Build Definition Name: Prereq Test Build number - all
Agent - Private (VM Environment) on Windows Servers:

Issue Description

Task version 2.170.0 fails to upload tasks, even though it completes successfully.

“Normal” log:

C:\azagent\A1\_work\_tasks\PublishTestResults_0b0f01ed-7dde-43ff-9cbb-e48954daf9b1\2.170.0\modules\TestResultsPublisher.exe @C:\azagent\A1\_work\_temp\40166ab0-a773-11ea-b9d3-91ff84b586bc.txt 
Finishing: Upload test reports

With diagnostic logs on, we see the following:

##[debug]Exit code 2148734720 received from tool 'C:\azagent\A1\_work\_tasks\PublishTestResults_0b0f01ed-7dde-43ff-9cbb-e48954daf9b1\2.170.0\modules\TestResultsPublisher.exe' 
##[debug]STDIO streams have closed for tool 'C:\azagent\A1\_work\_tasks\PublishTestResults_0b0f01ed-7dde-43ff-9cbb-e48954daf9b1\2.170.0\modules\TestResultsPublisher.exe' 
##[debug]Exit code of TestResultsPublisher: 2148734720 
##[debug]Agent.Version=2.169.1 
##[debug]Agent.TempDirectory=C:\azagent\A1\_work\_temp 
##[debug]Unable to publish the test run summary to evidencestore, error details:Error: ENOENT: no such file or directory, open 'C:\azagent\A1\_work\_temp\PTR_TEST_RUNSUMMARY.json' 
##[debug]task result: Succeeded

It appears that the code is looking for the PTR_TEST_RUNSUMMARY.json but this file does not exists. I took a quick scan through the repo and can only find this instance of reading the file - but not where the file is produced.