ApexTestResult Record not created when a testcase fails with RunningForTooLongException
Trailblazer Community

ApexTestResult Record not created when a testcase fails with RunningForTooLongException


Last updated 4 days ago ·Reference W-7834236 ·Reported By 112 users

Fixed - Summer '21

When executing Apex tests in parallel mode, unit tests sometimes deadlock and fail in multiple ways. Some tests fail with a fairly well-known "unable to obtain exclusive access to this record" message while interacting with normal sObjects ; others fail with a "connection was cancelled here" message , and do so without generating the proper Tooling API result records

This issue manifests typically when significant volume of Apex test runs in parallel mode

1.Create an org. Scratch org or developer edition should work fine. Ensure that parallel Apex testing is turned on.
2.Execute a unit test run. Any Tooling API `runAsynchronous` call should work the same provided it enqueues all of the Apex unit tests in the product in one run; doing a Run All in the Developer Console works fine for reproduction purposes.

3. Wait for the bulk of the unit test run to complete. You may see the test run spin forever, depending on the specific testing tool you utilize. The Apex Test Execution section of Setup will show the real situation with class-level failures.

Some Apex unit tests fail with messages that include the phrase "unable to obtain exclusive access to this record", related to ordinary sObject records that are being inserted by this test. These failures show up consistently across test UIs, as expected; they should have valid ApexTestQueueItem and ApexTestResult records found via the Tooling API.

Some Apex unit tests fail in a way that only shows in specific test UIs. The ApexTestQueueItem records for their parent classes will show Status = Failed and ExtendedStatus = "Could not run tests on class <01p class id> because: connection was cancelled here".
For these tests in, ApexTestResult records will usually not be created, although some may exist. It's these tests that show as in progress forever in tools like Salesforce DX and the Developer Console, which are looking for ApexTestResult records. One consequence is that many testing tools will report a different number of unit tests completed from run to run, due to monitoring ApexTestResult records


Reported By (112)

Niels Keuning Jonathan Helm James Hadfield John Daniel Azlam Abdulsalam Paul Jensen Kevin Hu Josh Bowman Laurel Jones Danielle LeRay Jennifer Wescott Matthew Cottrell Candace Guido January Chadwick Aellon Krider Omar Ghaznavi Aaron King Lando Toothman Bryan Mitchell Rachel Stephenson Christopher Tice Alagu arumugam Chellappa Tristan Pease Hem Nepal Jason Walke Bailey Wolford David Ciezki Raymond Cox iii Sharon Ebell Kenny Knapp Larry Gawlik Audrey Bunn John Stamets Charles Brooks Melissa Joyce Chris Edwards Kai Amundsen Boris Kretonic Emily Shull Terri Ilaria Dylan Menchetti Matthew Hivner Noah Crouch TJ Huels Dean Cooper Tyler Atkinson Benjamin Johnson Jeff Faber Rolf Locher Steven Powell William Jamar Bradley Esselman Karen Dana Adam Elders Phillip Byram Tracy Bragdon Kevin Watson Anna Muse Trey Wilson Justin McCotter Ryan McIntyre Brian Triplett Cameron Goodman Jose Jimenez Sushanth Kallem Irfan Junaid Costeijn Kuhlmann Jacob Peterson Karthik Pedditi Michael Karcz Brandon Vidro Justin Stouffer Josh Cartwright Kevin Carr Dan Carmen Shane Smalldon Noris Pasic David Simpson Trevor Roy Ali Rende Renaud Guillan Ashmi George Surya R Steven Ahrens Debanjan Sharma Bhrigu Bansal Rahul Khosla Apurva Jain R T Dilip Athley Almir Junior Philipstafford Jones Elavarasan Aravendan Vani Kota Swaran Kumar Poladi Ashoka Poojari Desmond Li Jason Brown Rob Hobkirk Nick Snyder Scott Harbaugh Stacy Beckmann greg jensen Todd VanGilder Michael Boyle Jason Hinson Craig Ceremuga Leonardo Santos Doug Ayers Daniel Ballinger Michael McNeeley Pasan Eeriyagama

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 CS1 CS2 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS167 CS166 CS16 CS169 CS165 CS160 CS173 CS17 CS172 CS170 CS171 CS174 CS18 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS209 CS200 CS202 CS201 CS203 CS21 CS219 CS218 CS217 CS216 CS215 CS214 CS213 CS212 CS211 CS210 CS22 CS220 CS23 CS234 CS24 CS25 CS26 CS27 CS28 CS29 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS53 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS99 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU44 EU45 EU46 EU47 EU48 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA161 NA163 NA167 NA160 NA166 NA165 NA169 NA164 NA168 NA162 NA172 NA170 NA174 NA171 NA173 NA196 NA207 NA204 NA206 NA208 NA209 NA21 NA218 NA214 NA217 NA215 NA212 NA213 NA210 NA65 NA70 NA71 NA75 NA80 NA81 NA82 NA83 NA84 NA85 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7 UM8 UM9

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.