You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an old organization with a lot of integration tests that take a while to execute (say between 40' and 60' on the main org). We have set up a Continuous Integration process based on the Saleforce CLI so that these tests are executed (on a Scratch Org) every time a commit is pushed to our repository. As our tests take a long time we use the wait parameter on the force:apex:test:run command to avoid a timeout (-w120 so that we have some leeway).
Lately (but I sadly cannot pinpoint from when exactly) our tests have been failing consistently:
the message for failure is "Your request exceeded the time limit for processing. connection was cancelled here" on ~80% of the failing tests.
the execution time of the force:apex:test:run command is exactly 60' every time.
We have tried to set a much larger value to the wait parameter but the tests get cancelled at the same point. We have tried to set the wait parameter to a very short value (1') and the command still seems to execute for a very long time.
Steps To Reproduce:
Set up a Scratch Org with tests.
Execute the tests on the Scratch Org: sfdx force:apex:test:run -w1 -lRunLocalTests
Expected result
sfdx force:apex:test:run -w1 -lRunLocalTests should cancel the run after ~1'.
sfdx force:apex:test:run -w120 -lRunLocalTests should execute all tests.
Actual result
The tests execute for what seems to be a default amount of time (60') whatever the value of wait.
Thanks for logging this! We did some testing of an older version of the CLI, and confirmed that it did respect that parameter. A cursory glance over the new code + some additional testing, and we're seeing the same as you, so we'll get this one into the backlog to address.
Hi @mcartoixa thanks for the nudge on this one! We haven't fixed this one just yet, but I'm linking the work here (W-11452324) so we can keep better track of resolving it. We'll continue to keep this issue updated as we're able to fix this!
Summary
We have an old organization with a lot of integration tests that take a while to execute (say between 40' and 60' on the main org). We have set up a Continuous Integration process based on the Saleforce CLI so that these tests are executed (on a Scratch Org) every time a commit is pushed to our repository. As our tests take a long time we use the wait parameter on the force:apex:test:run command to avoid a timeout (
-w120
so that we have some leeway).Lately (but I sadly cannot pinpoint from when exactly) our tests have been failing consistently:
We have tried to set a much larger value to the wait parameter but the tests get cancelled at the same point. We have tried to set the wait parameter to a very short value (1') and the command still seems to execute for a very long time.
Steps To Reproduce:
sfdx force:apex:test:run -w1 -lRunLocalTests
Expected result
sfdx force:apex:test:run -w1 -lRunLocalTests
should cancel the run after ~1'.sfdx force:apex:test:run -w120 -lRunLocalTests
should execute all tests.Actual result
The tests execute for what seems to be a default amount of time (60') whatever the value of wait.
Additional information
Apex library Version:
OS and version:
The text was updated successfully, but these errors were encountered: