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. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Canceled Execution continue In Progress

Discussion in 'Unity Simulation' started by mjnf, Aug 27, 2020.

Thread Status:
Not open for further replies.

  1. mjnf

    mjnf

    Joined:
    Feb 7, 2020
    Posts:
    8
    Hi,

    My simulation only take 5 seconds but never stop, I'm not sure about the problem. I canceled the execution and wait for 30 min, but looks like 8 runnings still in progress. It is normal ?

    Execution status: Cancelled(SchedulerService)
    state count
    ------------- -------
    Successes 0
    In Progress 8
    Failures 0
    Not Run 2
    Timed Out 0
     
    Last edited: Aug 27, 2020
    mjnf, Aug 27, 2020
    #1

  2. UnityShaunDon

    UnityShaunDon

    Unity Technologies

    Joined:
    Mar 8, 2019
    Posts:
    6
    Hi mjnf, Thanks for your report. We are aware of the inconsistency between cancelled run-execution status and the status of simulation-instances and a resolution will be forthcoming to correct it. For now, it is safe to consider your simulation-instances as no longer 
    InProgress
    when the Execution status is 
    Cancelled
    .

    If you can provide more detail about how you are stopping your simulation perhaps we can help to understand why it is executing for longer than you expect.

    For future reports may I kindly suggest that new posts be made in the Unity Simulation forum.
     
    UnityShaunDon, Aug 27, 2020
    #2

  3. mjnf

    mjnf

    Joined:
    Feb 7, 2020
    Posts:
    8
    I create this definition and run my build.
    Code (JSON):
    1. {
    2.     "name": "Test Run Definition",
    3.     "description": "This is a run definition for testing",
    4.     "build_id": "4w6oVa3",
    5.     "sys_param_id": "gcp@cpu:6+gpu:nvidia-tesla-t4:1",
    6.     "app_params": [{
    7.         "id": "DegVaL9",
    8.         "num_instances": 10
    9.     }]
    10. }
    My build has a 5 seconds time limit. But after 30 min the simulation had still in progress. I stopped it and ran again and it worked without problems the following definition with same params:

    Code (JSON):
    1.  
    2. {
    3.     "name": "test-def-1",
    4.     "description": "Test Def 1",
    5.     "build_id": "4w6oVa3",
    6.     "sys_param_id": "gcp@cpu:6",
    7.     "app_params": [{
    8.         "id": "DegVaL9",
    9.         "num_instances": 1
    10.     }]
    11. }
    12. ]}
    I create the original post in Unity Simulation and yadanathiri move it here. I don't know why :|

    Thanks !
     
    mjnf, Aug 28, 2020
    #3

  4. UnityShaunDon

    UnityShaunDon

    Unity Technologies

    Joined:
    Mar 8, 2019
    Posts:
    6
    It does look like the sys-param that has nvidia-tesla-t4 may be related to this undesired behavior. I will follow up on this later today.
     
    UnityShaunDon, Aug 28, 2020
    #4

  5. jamesfort

    jamesfort

    Unity Technologies

    Joined:
    Feb 3, 2020
    Posts:
    7
    Hello, I'm the product manager for our simulation solution and I've been in conversations with our support team about this issue. In parallel with the help that you are getting to resolve this, I would be interested in having a conversation with you about your use case. I understand that you want to run an HDRP project on our system. We can help you do that and I'd just like to understand more about your requirements and usage plans more generally. If you're open to that, can you provide an email address so we can schedule something?

    Thanks,
    James Fort
     
    jamesfort, Aug 31, 2020
    #5

  6. stevenke_unity

    stevenke_unity

    Unity Technologies

    Joined:
    Nov 13, 2018
    Posts:
    30
    stevenke_unity, Nov 12, 2020
    #6
Thread Status:
Not open for further replies.