Bug in Cloud Build? Build Fails with 'detected broken kqueue'

Unity Services
,
1

Unity staff, please help:
We were recently requested to update some Android settings. The changes seemed minor, but Cloud Build Fails with this right away and it seems to NOT be related to Android at all, but activating the license?!

Requesting Unity licenses for this machine…
[2023-04-04T16:44:37.435Z] - 7.3.4.2.4.2 - INFO: ++++++++++++++++++++++++++++++++++++++++
[2023-04-04T16:44:37.435Z] - 7.3.4.2.4.2 - INFO: + Acquiring Unity License
[2023-04-04T16:44:37.435Z] - 7.3.4.2.4.2 - INFO: ++++++++++++++++++++++++++++++++++++++++
[2023-04-04T16:44:37.435Z] - 7.3.4.2.4.2 - INFO: Attempting to activate a legacy license
[error] [2023-04-04T16:45:06.072Z] - 7.3.4.2.4.2 - DEBUG: [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[error] [2023-04-04T16:45:06.072Z] - 7.3.4.2.4.2 - DEBUG: [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[error] [2023-04-04T16:45:06.072Z] - 7.3.4.2.4.2 - DEBUG: [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[error] [2023-04-04T16:45:06.072Z] - 7.3.4.2.4.2 - DEBUG: [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[error] [2023-04-04T16:45:06.072Z] - 7.3.4.2.4.2 - DEBUG: [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[2023-04-04T16:45:06.072Z] - 7.3.4.2.4.2 - DEBUG: debugger-agent: Unable to listen on 55
[2023-04-04T16:45:06.157Z] - 7.3.4.2.4.2 - INFO: [04/Apr/2023:09:45:06] Sent Unity activation metrics
[2023-04-04T16:45:09.399Z] - 7.3.4.2.4.2 - INFO: ++++++++++++++++++++ SECTION ++++++++++++++++++++
[2023-04-04T16:45:09.399Z] - 7.3.4.2.4.2 - INFO: + Configuring Build Attempt
[2023-04-04T16:45:09.399Z] - 7.3.4.2.4.2 - INFO: ++++++++++++++++++++ SECTION ++++++++++++++++++++

Help!

2

Those are just warnings and have no impact on the build. If we were not able to activate a license at that point we would have exited the build and not continued into the configuration.

1 Like
3

Thanks. It was misleading because those entries were in red and prefixed with [error], but yes, that was not the cause of failed builds. (Since worked out and fixed). thanks!