An error occurred while resolving packages

[TomazTreven]

Hey,

We are having issues building our projects on Jenkins server. The issue seems to be that packages are not getting resolved. Sometimes it works and sometimes it fails.
Example of such failure:

2019-12-05 03:02:50.557 An error occurred while resolving packages:
2019-12-05 03:02:50.557 One or more packages could not be added to the local file system:
2019-12-05 03:02:50.557 com.outfit7.editor.build-tools: ENOENT: no such file or directory, scandir ‘C:\Users\jenkins\AppData\Local\Unity\cache\packages.…\repository\editor.build-tools@1.0.0’
2019-12-05 03:02:50.557 com.unity.editorcoroutines: [C:\Users\jenkins\AppData\Local\Unity\cache\npm\packages.unity.com\com.unity.editorcoroutines\0.0.2-preview.1\package.tgz] is not a valid package tarball.
…

But then again the same project in different workspace (with just different script define symbols (sometimes it fails in project with one set of defines and sometimes in another, so this probably isn’t an issue)) 18 minutes later succeeds:

2019-12-05 03:19:16.315 [Package Manager] Done resolving packages in 5.75s seconds
2019-12-05 03:19:16.315 [Package Manager]
2019-12-05 03:19:16.315 Registered 36 packages:
…
2019-12-05 03:19:16.317 [XR] No new subsystems found in resolved package list.
2019-12-05 03:19:16.317 [Package Manager] Done registering packages in 0.02s seconds

It’s interesting that this happens mostly for nightly jobs, when multiple different projects are building. If the issue is with high load/timeout/… when npm is resolving packages, could there be more settings for controlling this, to retry package resolving, or could there be any other cause or possible workaround?
We are running a lot of projects that could overlap, there is no virtualization involved.

Kind regards

[rscaldas]

Hi. Did you manage to solve this? We are having the same issue - except it fails every time. Any workarounds?

We are having this problem since we added a package from a git repo (Unity - Manual: Git dependencies).

[AskCarol]

Sorry you are both having this issue. Will circulate internally!
Thanks for your patience.

[roberto_sc]

At first I had a credentials problem that was fixed. But then the no subsystems found message kept appearing and it was making me believe I still had a problem with the package manager, while my project was broken for another reason. So I simply fixed that and everything is fine. The message was fooling me.

[okcompute_unity]

@TomazTreven

If the issue is with high load/timeout/… when npm is resolving packages, could there be more settings for controlling this, to retry package resolving, or could there be any other cause or possible workaround?

Improving network operations robustness is definitely on our roadmap.

Regards,

Pascal

[KenDots]

Hello,

We are having this problem with builds randomly failing as well with Unity 2019.4.16f1 - any updates or solutions for this issue?

Thanks!

[maximeb_unity]

@KenDots

Hello,

We are having this problem with builds randomly failing as well with Unity 2019.4.16f1 - any updates or solutions for this issue?

Thanks!

Hi @KenDots ,

I’m sorry you’re running into these instability issues. If you haven’t done so already, I would suggest you open a Bug Report in which you attach the project manifest.json and packages-lock.json (both found under the Packages directory), as well as the Editor.log and upm.log files of one such failing build. It may also help to turn on very detailed logging if this is an automated build by passing -enablePackageManagerTraces to Unity (but be warned that this will result in very large upm.log file, not recommended for normal day-to-day usage). (Note: no need to provide a repro project; the files above should be sufficient, at least as a starting point.)