Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Error: Bad runner encountered, please resubmit the job.

Discussion in 'Unity Build Automation' started by thibouf, Aug 4, 2020.

  1. thibouf

    thibouf

    Joined:
    Mar 17, 2017
    Posts:
    105
    I just got this error. The build has failed .

    Instead of failing, can't you just automatically restart the same build, on a good runner ???
     
    JonBFS and dirty-rectangle like this.
  2. kexar66

    kexar66

    Joined:
    Feb 27, 2013
    Posts:
    48
    The same here, started to happen today.
     
    JonBFS likes this.
  3. firegate666

    firegate666

    Joined:
    Nov 20, 2015
    Posts:
    19
    All my app bundle builds for Android fail in that way. APK and iOS IPA is working fine. I never gt a good worker

    1: Running Prebuild steps
    2: In quiet period, build will start momentarily...
    3: Using /BUILD_PATH/.rvm/gems/ruby-2.4.2
    4: Successfully uninstalled bvr-2.0.9
    5: Successfully uninstalled bvr-3.0.13
    6: Successfully uninstalled bvr-3.0.25
    7: Successfully uninstalled bvr-3.0.35
    8: Successfully uninstalled bvr-3.0.56
    9: Removing bvr
    10: Removing bvr_runner
    11: Successfully uninstalled bvr-3.0.71
    12: bvr 3.0.90
    13: bvr-api 0.3.18
    14: Error: Bad runner encountered, please resubmit the job.
    15: Build step 'Execute shell' marked build as failure
    16: Using /BUILD_PATH/.rvm/gems/ruby-2.4.2
    17: postbuildstatus finished successfully.
    18: postbuildsteps finished successfully
    19: Finished: FAILURE
     
  4. JonBFS

    JonBFS

    Joined:
    Feb 25, 2019
    Posts:
    39
    I retried shortly after my failed and it built fine.
     
  5. victorw

    victorw

    Unity Technologies

    Joined:
    Sep 14, 2016
    Posts:
    459
    FYI this issue should be extremely rare - like less than 0.1% of builds, realistically 0% most days unless something has gone wrong. We could automatically restart the build on a good runner but that would be complex to implement and since these errors are always avoidable on our end we would prefer to spend that effort trying to prevent this from ever happening in the first place.

    In this case we took a look at the builds where you experienced it and saw that you were all landing on the same builder, which was a dead node that didn't get cleaned up properly. We've cleaned up that node and are doing some work to ensure that no future builders wind up in that same state.
     
    dirty-rectangle and JonBFS like this.
  6. thibouf

    thibouf

    Joined:
    Mar 17, 2017
    Posts:
    105
    Ok thank you for the feedback.
    However , I really think you should add a way to automatically restart a build when something is wrong on the UCB side.
    Maybe this particular error is rare, but it not rare to have a build that failed due to some "unexpected error"
    Exemple :
    An internal Unity Cloud Build error has occurred (Unexpected termination of the channel). The Unity Cloud Build team is addressing this issue, and this build can be restarted if needed.
    As a user point of view, the problem is the same : UCB failed randomly, it is not a reproducible problem with my project So I don't see any reason not to try again automatically. (That is what I will do manually anyway...)
     
  7. jmguillemette

    jmguillemette

    Joined:
    Mar 4, 2015
    Posts:
    53
    Run into this a few times while trying to troubleshoot another build issue. retry the build again and the runner appears to work.
     
  8. IARI

    IARI

    Joined:
    May 8, 2014
    Posts:
    70
    Same issue on two builds - that doesn't seem that rare to me.
     
  9. neil_sublime

    neil_sublime

    Joined:
    Jul 9, 2018
    Posts:
    17
    We've had quite a lot of these over the past couple of weeks. Along with the builds getting automatically cancelled, the day when notifications weren't being sent to Teams, and other random failures, we've had a rough time with Cloud Build lately.
     
  10. Trivium_Dev

    Trivium_Dev

    Joined:
    Aug 1, 2017
    Posts:
    78
    I've also encountered 2 "Error: Bad runner encountered, please resubmit the job." within the last few days, and just had one happen today. I've never seen it before and I've done 1000s of builds. I'll occasionally get the "something went wrong with UCB, the build can be restarted".
     
  11. victorw

    victorw

    Unity Technologies

    Joined:
    Sep 14, 2016
    Posts:
    459
    Yeah we're going to have to temporarily roll back the changes which introduced this error until we get the entire builder lifecycle under control.
     
    rajantande likes this.
  12. Shredsauce

    Shredsauce

    Joined:
    Apr 4, 2016
    Posts:
    37
    In the past 3 days I've made 13 WebGL builds and it's happened to 3 of them.
     
  13. pawelduda

    pawelduda

    Joined:
    Feb 1, 2019
    Posts:
    45
    We had one bad runner daily this week...

    Most of them on MacOS builds though.
     
  14. midhapulkit28

    midhapulkit28

    Joined:
    Jan 18, 2019
    Posts:
    9
    I just got this error today for the first time
     
  15. unity_320AC700C5AB25D195F1

    unity_320AC700C5AB25D195F1

    Joined:
    Nov 19, 2021
    Posts:
    15
    FWIW, maybe a slightly different cause to above since the error related to floating licences:

    Code (CSharp):
    1. [warning] [2023-02-10T09:40:19.704Z] - 7.2.6.2.7.4 - WARN: Failed to acquire pooled license. Falling back to legacy
    2. [2023-02-10T09:40:19.704Z] - 7.2.6.2.7.4 - INFO: Attempting to activate a legacy license
    3. [error] [2023-02-10T09:40:49.951Z] - 7.2.6.2.7.4 - ERROR: Unable to activate legacy license
    4. [2023-02-10T09:40:49.951Z] - 7.2.6.2.7.4 - INFO: Sleeping 30 seconds and then checking again for a license.
    5. [2023-02-10T09:41:19.952Z] - 7.2.6.2.7.4 - INFO: Sleeping 30 seconds and then checking again for a license.
    6. [2023-02-10T09:41:49.953Z] - 7.2.6.2.7.4 - INFO: Sleeping 30 seconds and then checking again for a license.
    7. [error] Error: Unlicensed runner encountered, please resubmit the job.
    We've started seeing this error multiple times per day since earlier this week. Given the increased frequency of this error is there something we need to action, or just instability in UCB backend this week? Thanks