Builds and Tasks

Inspect, re-run, and manage every build and task that has run on the Signaloid Cloud Compute Engine.

Overview

Terminology

A Build is one compilation of your source code on the Signaloid Cloud Compute Engine. A Task is one execution of the resulting binary. A successful Build is reusable, so you can launch new Tasks from it without compiling again.

The Builds and Tasks page is the reference UI for every build and task attached to your account, whether the run started from the Code Playground, from a connected repository, or from the Compute Engine API. For a guided walkthrough, see How to Review Build and Task History.

The page has two tabs: Tasks (the default) and Builds. Each tab splits into an Active section for runs still in flight and a Completed section for finished runs. The Builds and Tasks sidebar item carries a badge with the combined count of active tasks and active builds, so you can track in-flight work without leaving the page you are on.

Figure 1. The Builds and Tasks page, showing the Tasks tab and Builds tab with their Active and Completed sections.

Status chips

Every card carries a status. The Compute Engine reports the same set on Tasks and on Builds:

• Initialising, Accepted, In Progress, Rescheduled mark runs that the Compute Engine has not finished yet. These runs land in the Active section.
• Completed marks a successful run.
• Cancelled marks a run you stopped.
• Stopped marks a run the Compute Engine ended early, for example after exceeding a tier limit.
• Error, Tier Limit Reached, and (on Tasks only) Task Rejected or Task Not Found mark terminal failures.

Hovering the duration chip on a card opens a tooltip with the full status timeline, so you can see the timestamps for every transition the run went through.

Tasks tab

The Tasks tab lists every execution on your account. Each card identifies the run, links back to its source, and lets you inspect or re-run it.

Each card shows:

• The task ID, prefixed with tsk_, with Copy ID ().
• The Signaloid core the task ran on, with a hover tooltip that expands the core's full specification.
• The source linkage. Code Playground tasks carry a Code Playground label and the line count of the source. Repository tasks carry a link to the repository, the branch, the commit, and the build directory.
• Timing chips: the queued or start timestamp, the wall-clock duration, and (on Completed tasks) the C0 execution time and the dynamic instruction credits the task consumed.
• The command-line arguments the task ran with.
• A warning indicator that opens a tooltip with the error message, on tasks that completed with a remote error.

The action row carries:

• Show Details opens the Task Detail page.
• On active tasks, Cancel stops the run.
• On terminated tasks, Remove task from history () deletes the task record after a confirmation.

Task detail page

The Task Detail page is where you read the output of a task. The route is /tasks/<task ID>. The page opens with a breadcrumb back to the Builds and Tasks page, the same card you saw on the Tasks tab, and a Results Panel underneath.

The page carries the same Results Panel as the Code Playground, showing stored output rather than a live run. Its Build tab holds the build that produced this task's binary.

Figure 2. Opening a task's detail page, hovering and clicking values in stdout to see their distributions, toggling Show Plots, and canceling an in-flight task.

Builds tab

The Builds tab lists every compilation on your account. The card on a successful build is also a launch pad. You can start a new task from it without recompiling.

Each card shows:

• The build ID, prefixed with bld_, with Copy ID ().
• The Signaloid core the build targeted.
• The source linkage, mirroring the Tasks tab.
• Timing chips: the queued or start timestamp and the build duration.
• The default command-line arguments stored on the build.
• For Code Playground builds, the compilation and link flags from config.mk.

On a Completed build, the action row also has:

• Run Task starts a new task immediately, using the build's stored default arguments and data sources.
• View Outputs (), available once you have run a task from this card, opens the Execution Results dialog with the task's output. The dialog wraps the same Results Panel the Code Playground uses.
• Command-Line Arguments () opens a dialog where you edit the arguments to use for the next task you launch.
• Mount Data Source () opens a dialog where you attach a data source to the next task you launch.
• Delete build () deletes the build after a confirmation.

On a failed or canceled build, only the Delete build action remains.

Figure 3. Running a new task from a completed build with edited command-line arguments.