Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Activate License Task log output misses last package manager output messages #214

Open
ikriz opened this issue Dec 6, 2022 · 1 comment

Comments

@ikriz
Copy link

ikriz commented Dec 6, 2022

Quite often I run into issues with the activation task it fails with an error and the last message in the log is:

Rebuilding Library because the asset database could not be found!
Unwatch C:\projectpath\Logs\UnityActivationLog_2022-12-05-17-26-47.log
The process 'C:\Program Files\Unity\Hub\Editor\2021.3.11f1\Editor\Unity.exe' failed with exit code 1
=============================== UNITY LOG END ================================
The Unity process failed with exit code -1
##[error]The Unity process failed with exit code -1
Finishing: UnityActivateLicenseTask

Where as when I check the actual log output there is still output from the packagemanage which is completely missed?

Rebuilding Library because the asset database could not be found!
[Package Manager] Done resolving packages in 51.22s seconds
An error occurred while resolving packages:
  Project has invalid dependencies:
    redacted: connect ETIMEDOUT ip:port
    redacted: connect ETIMEDOUT ip:port

A re-import of the project may be required to fix the issue or a manual modification of C:/projectpath/Packages/manifest.json file.
Exiting without the bug reporter. Application will terminate with return code 1
@bdovaz
Copy link
Contributor

bdovaz commented Dec 6, 2022

I have been experiencing the same problem for some time now.

But actually it has nothing to do with licenses but with any execution of the Unity process through the tasks in this repo.

It's as if the log watcher is always missing the UPM logs.

As a workaround we have chosen to create artifacts of the logs to be able to access them without at least logging into the agents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants