Skip to content

CI flake: Unity WebGL build #6540

Closed as duplicate
Closed as duplicate

Description

@clockwork-labs-bot

Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.

Tests:

  • Unity WebGL build

Error:
[Licensing::Module] Error: License is not active (com.unity.editor.headless). HasEntitlements will fail.
Pro License: NO

Failed job runs:

Timeout detection:

  • none

Context:

  • none

Activity

  1. clockwork-labs-bot commented on Nov 9, 2026

    @clockwork-labs-bot
    ContributorAuthor

    Symptoms and root cause

    Exact failed job: run 42693137728, job 129423072517, attempt 1, Unity WebGL build.

    • Setup and SDK hydration succeeded. Unity initially activated its license (Pro License: YES) and completed the preparation invocation.
    • The subsequent build invocation reported Access token is unavailable; failed to update, then License is not active (com.unity.editor.headless). HasEntitlements will fail., Pro License: NO, and No valid Unity Editor license found. Please activate your license. The build exited 1 before the WebGL build proper.
    • The later Seat id doesn't belong to user error occurred during license-return cleanup, after the build failure; it is not the primary failure. Why the license became unavailable between invocations is unproven.
    • Attempt 2, job 129442302442, retained Pro License: YES and built successfully. This is a Unity licensing/environment failure, not an observed SpacetimeDB test assertion or cancellation.

    Duplicate selection

    Selected the still-open canonical root #5581. Its retained diagnosis has the same explicit inactive-headless-license / no-valid-Editor-license rejection, followed by the same seat-return cleanup symptom. The manifestation differs only in the Unity entry point: this ticket builds WebGL; the root ran the test suite. Matching specific rejection diagnostics support grouping without claiming a proven shared underlying cause.

    Searched all 98 open issues across the entire 991-item Test flakes project, plus organization-wide open diagnostic searches. The root has 9 distinct incoming canonical duplicate relationships on its own timeline. No closed issues were inspected. #5302 lacks a confirmed primary failure; #5913 and #5919 instead have explicit serial activation-limit and serial-not-assigned rejections, so they are not the selected match.

    Proposed operations

    Applied and independently verified after explicit human approval (2026-11-10):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions