[Horde] Auto-Submit on Preflight success

Development Pipeline & Plugins
, ,
1

I am trying the auto submit on success of the Preflights, which fails all the time… but I can’t get the logs for that step. I can’t see it on the log server or in the job’s steps.

I added :

“Logging”: {

“LogLevel”: {

“Default”: “Debug”,

“EpicGames.Horde”: “Debug”,

“EpicGames.Perforce”: “Debug”,

“EpicGames.Core”: “Debug”

},

“IncludeScopes”: true

}

I can find the jobID in the logs and when it jumps from a status to another, yet… nothing about the submit.

Any ideas?

2

Steps to Reproduce
1 - Using Unreal P4V Utils - Preflights, start one.

2 - In the window, you should have the option to Auto-Submit files on Success

3

Hey there,

AutoSubmitChangeAsync [Content removed] a targeted Serilog configuration for the JobService:

  • Dependency injection via ILogger<JobService> logger
  • You’d add a entry for “HordeServer.Jobs.JobService”: “Debug” //or Information
  • For posterity, practical debugging tips for Horde more or less outlines this.
  • But again, you’ve set to debug as your default so this looks correct to me.

Are you able to attach remotely to your server and step through the code? If you’re comfortable adding more logging, you could try to add more to JobService at the callsite of AutoSubmitChangeAsync just to make sure you’re even issuing the call:

// JGAMBLE - DIVERGENCE START _logger.LogInformation("Evaluating check for preflight submit."); // JGAMBLE - DIVERGENCE END if (job.AutoSubmit && outcome == JobStepOutcome.Success && job.AbortedByUserId == null) { // JGAMBLE - DIVERGENCE START _logger.LogInformation("Initiating check for preflight submit."); // JGAMBLE - DIVERGENCE END job = await AutoSubmitChangeAsync(streamConfig, job, graph, cancellationToken); }Kind regards,

Julian

4

Heya Julian! I’ll try what you’re suggesting tomorrow morning and add more info… or the solution if I get it that way!

5

It’s been a while, sorry about that… it was a busy month!

I’ll do it this week.

However, I was wondering if modifying Horde’s code and redeploying the server for test purposes isn’t a bit overkill?

6

Hey there,

I’d say in general, yes. The only reason I suggest this is that I haven’t seen the preflight-autosubmit failure issue come up at all internally or through other licensees. One thing I can certainly say is that if this turns out to be a larger (more systemic issue), I could look at getting more additional logging added officially.

Thinking aloud on some ideas - does the horde server *user* have submission permissions?

Julian