Apex Test Report - Cannot read property 'records' of null

maaaaarco commented 3 years ago

Summary

force:apex:test:report fails with message: Cannot read property 'records' of null

Steps To Reproduce:

Run this command to schedule a full test run sfdx force:apex:test:run --codecoverage --resultformat=human --synchronous --testlevel=RunLocalTests
Run this command to check on the status sfdx force:apex:test:report --testrunid=707xxxxxxxxxxxx

You should get the error mentioned above.

Additional information

SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.102.0 darwin-x64 node-v16.1.0

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core) @oclif/plugin-autocomplete 0.3.0 @oclif/plugin-commands 1.3.0 (core) @oclif/plugin-help 3.2.2 (core) @oclif/plugin-not-found 1.2.4 (core) @oclif/plugin-plugins 1.10.0 (core) @oclif/plugin-update 1.4.0-3 (core) @oclif/plugin-warn-if-update-available 1.7.0 (core) @oclif/plugin-which 1.0.3 (core) @salesforce/analytics 0.23.0 @salesforce/lwc-dev-mobile 1.2.0 @salesforce/sfdx-trust 3.6.0 (core) alias 1.1.10 (core) auth 1.5.4 (core) config 1.2.8 (core) generator 1.1.5 (core) salesforcedx 51.12.0 (core) ├─ templates 51.3.1 (core) ├─ custom-metadata 1.0.12 (core) ├─ data 0.4.6 (core) ├─ apex 0.2.0 (core) ├─ user 1.2.10 (core) ├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core) ├─ org 1.6.5 (core) ├─ salesforce-alm 51.6.23 (core) ├─ schema 1.0.6 (core) └─ limits 1.2.0 (core) sfdx-cli 7.102.0 (core) telemetry 1.2.1 (core)

OS and version: MacOS 11.3.1

github-actions[bot] commented 3 years ago

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.

maaaaarco commented 3 years ago

P.S. The issue only appears if the full test run is in progress, once it's finished the command works as expected.

github-actions[bot] commented 3 years ago

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 commented 3 years ago

@AnanyaJha you can mark this as a bug and it'll create a gus WI. Or transfer it if you think it's in your plugin.

AnanyaJha commented 3 years ago

Hi @maaaaarco thanks for reporting this! This is a known issue and we're working on resolving it. Do you mind sharing what behavior this command had for you in the past? Did the command generally wait for the run to finish and successfully return the results or have you run into any errors ie. Socket timeouts?

maaaaarco commented 3 years ago

Hey @AnanyaJha , I was not using that command on a daily basis but what you said "...wait for the run to finish and successfully return the results..." this would be my expectation since we also have the --wait option on this command.

randi274 commented 2 years ago

@maaaaarco this was fixed a hot minute ago, but didn't get auto-closed; can you confirm this is working as expected for you now?

forcedotcom / salesforcedx-apex