Skip to main content

Session Dashboard

The Session dashboard is the operator view for Kerrigan workflow progress. It shows every submitted session, the current session state, task fanout, assigned DevKits, retry attempts, task results, and collected device logs.

Open Sessions​

In the dashboard, open Sessions. The left rail lists recent sessions with:

  • session name
  • session ID
  • source repository or local
  • elapsed or completed time
  • status badge
  • GitHub Actions marker when the session came from a runner bridge job

Use the search field to filter by session name, ID, repository, or other indexed session text. Use the state filter to focus on running, passed, failed, infra_failed, scheduler_failed, or cancelled sessions.

Read Session Progress​

Select a session to open the detail view. The header shows:

  • session ID
  • repository
  • elapsed/completed time
  • GitHub Actions run link when available
  • retention expiry
  • final or current status

The status strip summarizes task counts by state. Click a state in the strip to filter the task summary and task list to that state.

Task states:

  • queued: waiting for dependencies or capacity
  • assigned: assigned to a DevKit but not yet reported as running
  • running: actively executing on a DevKit
  • passed: completed successfully
  • failed: test command failed
  • infra_failed: infrastructure or agent failure
  • retry_pending: waiting for a configured retry
  • scheduler_failed: no eligible device or dependency failure
  • cancelled: cancelled by operator, runner bridge, or session policy

Test Summary​

The Test Summary table is usually the fastest way to understand a session. It shows:

  • task ID
  • assigned DevKit
  • result state
  • duration
  • attempts
  • exit code
  • summary or failure reason
  • collected log count

Click a task row to filter the log stream to that task. This is useful when a large workflow has many setup, test, and teardown events mixed together.

Tasks​

The Tasks panel shows the live task list, including generated setup and teardown tasks. For example, a manifest with setup.per_devkit creates setup tasks for each selected DevKit before normal tests run. A manifest with teardown.per_devkit creates teardown tasks once normal tasks reach terminal state.

The task list is capped in the UI for readability, but the session archive keeps the full task summary and log history while the record is retained.

Collected Logs​

The Collected Logs panel shows session events and device-agent output. Logs can include:

  • session scheduling events
  • waiting-for-capacity diagnostics
  • task assignment and completion
  • artifact download and extraction progress
  • Neat CICD Infrastructure (Vulcan) package installation progress
  • command stdout/stderr snippets forwarded by the device agent
  • scheduler rejection reasons when no eligible device exists

Use the DevKit filter to inspect logs from one device. Use a task row or task chip to inspect logs for one task.

When kerrigan-runner-bridge runs inside GitHub Actions, it attaches source metadata to the session, including workflow name, run ID, attempt, commit SHA, and run URL. The Session dashboard renders that as a GitHub Actions link in the session header.

Cancel Or Delete​

System Admins can cancel a running session. Cancellation requests stop queued work and mark active work cancelled as devices report back.

Completed session records can be deleted by System Admins. Live sessions cannot be deleted; cancel or wait for completion first.

Session archives are retained for seven days by default.