game-ci / unity-builder

Build Unity projects for different platforms
https://github.com/marketplace/actions/unity-builder
MIT License
857 stars 253 forks source link

Licensing::Module errors #611

Closed brookman closed 11 months ago

brookman commented 1 year ago

Bug description

Since yesterday around 80% of our CI builds fail with 2 different Licensing::Module errors. Around 1 in 5 builds succeed.

How to reproduce

Run any game-ci/unity-test-runner or game-ci/unity-builder action using a pro license on self hosted runners (Linux). Happens with versions 2.1.x as well as 2.2.0.

-

Expected behavior

All builds should succeed.

Additional details

Error case 1:

...
[Licensing::Module] Successfully connected to LicensingClient on channel: "LicenseClient-root" (connect: 0.68s, validation: 0.06s, handshake: 0.00s)
[Licensing::IpcConnector] Successfully connected to the License Notification on channel: "LicenseClient-root-notifications"
[Licensing::Module] Connected to LicensingClient (PId: 40, launch time: 0.00, total connection time: 0.75s)
Entitlement-based licensing initiated
[Licensing::Module] Error: Access token is unavailable; failed to update
[Licensing::Module] Error: Failed to activate entitlement license
[Licensing::Module] Error: Access token is unavailable; failed to update
[Licensing::Module] Error: Failed to activate ULF license
...

Error case 2:

...
[Licensing::Module] Successfully connected to LicensingClient on channel: "LicenseClient-root" (connect: 0.57s, validation: 0.11s, handshake: 0.00s)
[Licensing::IpcConnector] Successfully connected to the License Notification on channel: "LicenseClient-root-notifications"
[Licensing::Module] Connected to LicensingClient (PId: 42, launch time: 0.00, total connection time: 0.68s)
Entitlement-based licensing initiated
[Licensing::Client] Successfully updated the access token
[Licensing::Module] Successfully updated the access token XXX...
[Licensing::Client] Successfully processed license management request
[Licensing::Module] Successfully activated the entitlement license
[Licensing::Client] Successfully queried for the EntitlementGroupsDetails
[Licensing::Client] Error: Code 1500 while processing request (status: Internal Client Error: The delegate executed asynchronously through TimeoutPolicy did not complete within the timeout.)
[Licensing::Module] License activation has failed. Aborting.
...

Success case (20% of the time):

...
[Licensing::Module] Successfully connected to LicensingClient on channel: "LicenseClient-root" (connect: 0.66s, validation: 0.07s, handshake: 0.00s)
[Licensing::IpcConnector] Successfully connected to the License Notification on channel: "LicenseClient-root-notifications"
[Licensing::Module] Connected to LicensingClient (PId: 42, launch time: 0.00, total connection time: 0.[74](https://XXX/actions/runs/403588/jobs/646974#step:6:75)s)
Entitlement-based licensing initiated
[Licensing::Client] Successfully updated the access token
[Licensing::Module] Successfully updated the access token XXX...
[Licensing::Client] Successfully processed license management request
[Licensing::Module] Successfully activated the entitlement license
[Licensing::Client] Successfully queried for the EntitlementGroupsDetails
[Licensing::Module] We are skipping activation, because the license has already beed activated
[Licensing::Client] Successfully resolved entitlements
[Licensing::Module] Serial number assigned to: "XXXX"
Pro License: YES
...
SethCram commented 1 year ago

I'm also receiving the [Licensing::Module] Error: Access token is unavailable log message but it's followed up by [LicensingClient] Licenses updated successfully on the next line.

davidmfinol commented 1 year ago

We've recently made a lot of changes around license activation. Is this still an issue with v4 of the actions?