Search Unity

Package Manager timeout with CI Builds

Discussion in 'Package Manager' started by Stephen-Hodgson, Apr 17, 2019.

  1. Stephen-Hodgson

    Stephen-Hodgson

    Joined:
    Jul 15, 2014
    Posts:
    23
    I'm using Continuous Integration and just updated to 2019.1.0f2 and I'm getting some timeout exceptions with the package manager. Is there something I'm missing?

    Using Azure DevOps with a Hosted Windows VS 2017 instance with the latest bells and whistles.

    Code (CSharp):
    1. [Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [15] seconds
    2. [Package Manager] Server::Kill -- Server was shutdown
    3. [Package Manager] PackageManager Server::Start -- Process restart attempt #2
    4.  
    5. [Package Manager] Server::Start -- Port 61129 was selected
    6. DisplayProgressbar: Unity Package Manager
    7. [Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
    8. [Package Manager] Server::Kill -- Server was shutdown
    9. [Package Manager] PackageManager Server::Start -- Process restart attempt #3
    10.  
    11. [Package Manager] Server::Start -- Port 61130 was selected
    12. [Package Manager] Cannot connect to Unity Package Manager local server
    13. [Package Manager] Done resolving packages in 11.93s seconds
    14. An error occurred while resolving packages:
    15.   Project has invalid dependencies:
    16.     com.unity.package-manager-ui: Package [com.unity.package-manager-ui@2.1.2] cannot be found
    17.     com.unity.timeline: Package [com.unity.timeline@1.0.0] cannot be found
    18.   Package com.unity.analytics@3.3.2 has invalid dependencies:
    19.     com.unity.ugui: Package [com.unity.ugui@1.0.0] cannot be found
    20.   Package com.unity.textmeshpro@2.0.0 has invalid dependencies:
    21.     com.unity.ugui: Package [com.unity.ugui@1.0.0] cannot be found
     
  2. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    575
    Hi @Stephen-Hodgson,

    This is really strange. Some of the packages reported as
    cannot be found
    are built-in with the editor! They should be found. Can you debug your instance? If yes, please look into Unity install folder and look up for this sub-folder:
    /Resources/PackageManager/BuiltInPackages
    . All the missing packages you've listed should be there. If the folder is empty, then maybe there was an installation issue?

    Regards,

    Pascal
     
  3. Stephen-Hodgson

    Stephen-Hodgson

    Joined:
    Jul 15, 2014
    Posts:
    23
    Unfortunately I don't have access to the VM image.

    I'm essentially standing up a new install each time, and I'll double check if those resources actually exist.
     
  4. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    575
    Another possibility. You have saved your project locally with 2019.1. But your CI open the project with 2018.3 or an older version. Unity does not downgrade project data or package configurations. It only adapts your package configurations moving forward.
     
    dave_thrive and Stephen-Hodgson like this.
  5. Stephen-Hodgson

    Stephen-Hodgson

    Joined:
    Jul 15, 2014
    Posts:
    23
    Upon further investigation, that's exactly what was happening. Thanks for your time.
     
    okcompute_unity likes this.