Time out in Directed_3.0.1 work item

[JulieLeeMSFT]

Pipeline:

• Pipelines - Runs for runtime-coreclr gcstress-extra (azure.com)
• Pipelines - Runs for runtime-coreclr gcstress0x3-gcstress0xc (azure.com)

https://dev.azure.com/dnceng-public/public/_build/results?buildId=596943&view=results

> /root/helix/work/workitem/e/JIT/Directed/Directed_3/../StructABI/StructABI/StructABI.sh
22:46:14.055 Passed test: JIT/Directed/StructABI/StructABI/StructABI.cmd
22:46:14.116 Running test: JIT/Directed/tailcall/more_tailcalls/more_tailcalls.cmd
Invoking: sudo ls -l /home/helixbot/dotnetbuild/dumps/coredump.227.dmp.crashreport.json
stdout: -rw------- 1 helixbot2 adm 24482 Mar 10 22:46 /home/helixbot/dotnetbuild/dumps/coredump.227.dmp.crashreport.json

=========================================
Child process took too long. Timed out... Exiting...
App Exit Code: 110
Expected: 100
Actual: 110
END EXECUTION - FAILED
+ test_exit_code=1
+ dotnet /root/helix/work/correlation/XUnitLogChecker/XUnitLogChecker.dll --results-path JIT/Directed/Directed_3 --test-wrapper Directed_3 --dumps-path /home/helixbot/dotnetbuild/dumps
[XUnitLogChecker]: 03:43:06.41: The full run will be done.
[XUnitLogChecker]: 03:43:06.50: Item 'Directed_3' did not finish running. Checking and fixing the log...
[XUnitLogChecker]: 03:43:06.61: XUnit log file has been fixed!

237/245 tests run.
* 234 tests passed.
* 0 tests failed.
* 3 tests skipped.

[dotnet-policy-service]

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

[hoyosjs]

This isn't too much of an infrastructure issue, it's a timing issue - the tests took nearly 5 hours (22:42 to 3:42). We can adjust times a little so that the watcher is always guaranteed a few mins of processing time, but there's always a time window for this to occur.

[BruceForstall]

This is a dup of #99410