sfcli apex test run command is throwing an error "Error (10): Cannot read properties of undefined (reading 'Status')"

[RohitGagan16]

Summary

sfcli apex test run command is throwing an error "

• sf apex run test -o -l RunLocalTests -d {dir} -w 240 -r human -c
  Error (10): Cannot read properties of undefined (reading 'Status')"

Steps To Reproduce

IMPORTANT
First authenticate the user using salesforce cli. Use the authenticator token to run the following command

sf apex run test -o -l RunLocalTests -d {dir} -w 240 -r human -c

Expected result

This should give the test result report along with the coverage for each class

Actual result

It is throwing an error
"Error (10): Cannot read properties of undefined (reading 'Status')""

System Information

Jenkins linux agent

Salesforce cli version:

• sf --version
  @salesforce/cli/2.26.10 linux-x64 node-v18.17.1

[github-actions]

Hello @RohitGagan16 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[mshanemc]

That's coming from the Apex library. I'm going to transfer the issue to them. Thanks for reporting.

[RohitGagan16]

• sf --version --verbose --json
  @salesforce/cli/2.26.10 linux-x64 node-v18.17.1

[Rocko1204]

Hi @mshanemc @RohitGagan16 I have created the pull request #351 to resolve this issue. The error occurs very often hence the pull request. It doesn't solve the actual problem on the org, but it handles the module error.

[mingxuanzhangsfdx]

Hi @Rocko1204 Thanks for creating the PR, we will review it and get back to you soon.