Explicitly close the log file reader when an application terminates or has exited. This is make sure all log file handles are closed when another device comes along to potentially delete this log file.
#preflight 62d9b7cd4b6d775f5f076bf6
#preflight 62d9cf5f3122bf80ae18bdb9
#ROBOMERGE-AUTHOR: eric.knapik
#ROBOMERGE-SOURCE: CL 21212603 via CL 21213335 via CL 21214157 via CL 21214231
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v972-20964824)
[CL 21214664 by eric knapik in ue5-main branch]
#rnx
#jira none
#review-21186711 @brandon.schaefer
#rb @brandon.schaefer
#preflight 62d971d8bc175ec68c7c5d33
Details
- Previously UserDir was set in such a way that multiple gauntlet processes launched on the same machine would have their log directories collide. In the observed failure case, the client would launch after the server, stomping the server's log. Then gauntlet would be unable to find the test results and report as "No tests executed". This change just makes the path be the same as what Windows uses.
[CL 21201734 by james singer in ue5-main branch]
Fix a potential warning when two UAT commands are ran back to back in the build graph. This can result in files potentially not being immediately deleted.
#preflight 62d88523d54af4b9a2de539d
#rb: Chris.Constantinescu
#ROBOMERGE-AUTHOR: eric.knapik
#ROBOMERGE-SOURCE: CL 21195999 via CL 21197116 via CL 21197117 via CL 21197118
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v972-20964824)
[CL 21197500 by eric knapik in ue5-main branch]
#preflight skip
#ROBOMERGE-AUTHOR: andrew.grant
#ROBOMERGE-SOURCE: CL 21066766 via CL 21083532 via CL 21083910 via CL 21084171
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v972-20964824)
[CL 21086518 by andrew grant in ue5-main branch]
#jira UE-151756
#rb chris.babcock
#tests preflight replay run and ensure it copies the build and launches on android devices.
#preflight 62b0d2488e03312ad8367092
[CL 20743755 by j baumgartner in ue5-main branch]
#rb chris.babcock
#jira UE-151756
#tests Ran ReplayRun preflight and the job no longer had issues with build copy
#preflight 6297b1f6e809e387be23529b
[CL 20456799 by j baumgartner in ue5-main branch]
#rb J.Baumgartner
#ROBOMERGE-AUTHOR: william.ewen
#ROBOMERGE-SOURCE: CL 19119634 via CL 19119681 via CL 19119730 via CL 19123251
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v921-19075845)
[CL 19154352 by william ewen in ue5-main branch]
#rb J.Baumgartner
#ROBOMERGE-AUTHOR: william.ewen
#ROBOMERGE-SOURCE: CL 18854299 via CL 18854732 via CL 18854742 via CL 18855476 via CL 18855725
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v910-18824042)
[CL 18855752 by william ewen in ue5-main branch]
- skipClient option allows for client steps to be run in UAT with a null role which causes them to be skipped
- the test still runs and is considered successful and all dependencies are still executed
- this results in a "Null" client device with a null platform
- IDeviceUsageReporter causes exceptions with this configuration
- change IDeviceUsageReporter methods to take a platform reference and handle a null platform internally
- no events are logged for the null device and platform
- the null client device associated with teh skip tests will create a NullAppInstance
- NullAppInstance only completes upon WaitForExit() but many tests don't do this as they run until they see a specific line in the output log or something similar (ex: boot tests)
- this causes some NullAppInstance tests to never complete and to run until a timeout is encountered
- NullAppInstance is now considered completed and HasExited upon creation to resolve this
- the base test node then identifies the null app instance as completed
#rb Chris.Constantinescu, Josh.Engebretson, Jerome.Delattre
#jira none
#preflight https://horde.devtools.epicgames.com/job/61e1c430b14a67d611987c49
[CL 18648971 by eric mcdaniel in ue5-main branch]
