force:apex:test:run causes "Your request exceeded the time limit for processing. connection was cancelled here" errors when tests run in parallel. about salesforcedx-apex HOT 11 CLOSED

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

from salesforcedx-apex.

Thanks for the additional detail and troubleshooting @jclark-dot-org! I'll use a large suite to test the issue and see if I can reproduce it today. If I can't, it would be great to get a 30 day org set up where we can reproduce the issue consistently.

from salesforcedx-apex.

@randi274 Certainly. I'll spin up a fresh 30 day scratch and send the credentials to your SF email (as listed in your github profile).

from salesforcedx-apex.

Hey clark, Were you able to resolve this issue by contacting with the salesforce support directly? If so, can you provide us on details with how it got resolved and what the issue was?

from salesforcedx-apex.

@Mowrish No, I did not open a support ticket. At the time the team decided to put the issue into tech debt, and since that time I have moved off the project that had this issue. I don't know if the project team has resolved the issue.

However, I can point you at this Salesforce Stack Exchange post that has some information on the issue and possible ways of addressing. I believe both answers had some information. I have it bookmarked in case I run into this problem again.

https://salesforce.stackexchange.com/questions/264474/why-do-running-tests-in-parallel-makes-apex-cpu-timeout-possible-likely

from salesforcedx-apex.

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.

from salesforcedx-apex.

Hi @jclark-dot-org - you can disregard the support case instructions above, unless you need an SLA on this item. I've moved it to the apex library where we're best equipped to look at it now. When you run the tests in parallel in the org (vs using the CLI), do you encounter any similar issues?

from salesforcedx-apex.

@randi274 Thanks Randi. Since I reported this, I have tried to figure out how it performs, outside the CLI. We have some unlocked package code (which gets included by "Run Local Tests") in the org that we do not want to test. My solution was to create an Apex Test Suite containing the 318 Unit test classes which we want to run for CI.

I tested the suite using the CLI, and observed the same issue. Then I tested the suite using "New Suite Run" in Developer Console, and observed the same issue. Two things I have observed:

• The list of tests which fail with the time limit error is not always the same between runs
• A number of the test classes which seem to consistently fail are quite large, and we've added a tech debt item to break them up. However, other test classes with only one or two tests have exhibited the same error.

Let me know if you need to me quantify the observed results better, or if you'd like support access to an org where you can run the tests in question - I may be able to provide access to a dedicated scratch org, if the client agrees.

from salesforcedx-apex.

I wasn't able to get enough tests where this was an issue today @jclark-dot-org - if you can provide us an org where this is happening, that would be great to test and debug further 👍

from salesforcedx-apex.

Thanks for your patience and for providing an org for testing! I reached out to our Apex team on this issue, and they recommend opening a case with Salesforce support directly since the root cause of these errors can be different. With that in mind, I'll be closing this issue as it's not something that we can fix within this library.

from salesforcedx-apex.

+1

from salesforcedx-apex.