Crash report client's DataRouterUrl is not being used when a client hits an ensure during a Horde gauntlet test

Development Pipeline & Plugins
, ,
2

Steps to Reproduce

  1. Create a gauntlet test, let’s use UE.BootTest as an example
  2. UE.BootTest is configured to start up one client
  3. Make sure your client ensures upon startup(?). This step is a bit different project to project. I just happened to have a build that did this so I’m using it as my test candidate.
  4. Make sure CrashReportClient’s DefaultEngine.ini is setup with a DataRouterUrl that is linked to your crash listener (we are using a python server that listens, unpacks and handles crashes)
  5. Run gauntlet via RunUAT.bat. Here’s an example of how we do it:
    1. RunUAT.bat RunUnreal -project=“<path to uproject>” -test=“UE.BootTest” -platform=Win64 -build=“<path to package build>” -nullrhi
  6. Wait for ensure
  7. Watch ensure go through the crash handler
  8. End gauntlet run
  9. Schedule a gauntlet job via Horde. Here’s a snapshot of our build graph that is invoked by the job template:
    1. <Node Name=“Gauntlet”>
    2. <Command Name=“RunUnreal” Arguments=“$(ProjectPath) $(BuildPath) $(Platform) -nullrhi -WriteTestResultsForHorde” />
    3. </Node>
  10. Schedule the new job
  11. Watch the Horde logs. See that ensures are being detected.
  12. Ensures do not go through the crash handler :frowning: