sf apex run test --json is not returning testRunId

[VenkatNaveenM]

• testRunId is missing in json response. I suspect summary itself is missing.
• I saw a difference in Apex Test History in my org, after release Run id is showing on the history whereas before it is missing.
  image.
  

Please find below information:

SF Version - @salesforce/cli/2.0.2 linux-x64 node-v18.17.0

Command:
sf apex run test --test-level RunLocalTests --json > test_outcome_full.json --wait 180 --target-org "$(fullsandbox-username)"
echo "-- Test Summary --"
jq . test_outcome_full.json
echo "--------------------------------------"
testRunId=($(cat test_outcome_full.json | jq ".result.summary.testRunId" | tr -d '"'))
echo "Test Run Id: $testRunId"

Response:

-- Test Summary --
{
"code": 1,
"context": "Test",
"commandName": "Test",
"message": "
Bad Message 431
reason: Request Header Fields Too Large
",
"name": "ERROR_HTTP_431",
"status": 1,
"stack": "ERROR_HTTP_431:
Bad Message 431
reason: Request Header Fields Too Large
\n at HttpApi.getError (/usr/local/lib/node_modules/@salesforce/cli/node_modules/jsforce/lib/http-api.js:252:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async /usr/local/lib/node_modules/@salesforce/cli/node_modules/jsforce/lib/http-api.js:122:23\n at async Query._execute (/usr/local/lib/node_modules/@salesforce/cli/node_modules/jsforce/lib/query.js:413:18)\n at async /usr/local/lib/node_modules/@salesforce/cli/node_modules/jsforce/lib/query.js:346:9",
"exitCode": 1,
"warnings": []
}
Test Run Id: null

[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.

[github-actions]

Hello @VenkatNaveenM 👋 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!

[iowillhoit]

Hello @VenkatNaveenM,
Please follow all of the instructions on the bug creation template. Most importantly, updating to the latest version of sf and providing the full output of sf versions --verbose --json.

I am not seeing this locally. They 403 error is odd though, were you seeing that error before the last release? How many tests are you trying to run?

[github-actions]

This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.