orcaLog in

Runs · mojo_versions · ·

Run 5077 succeeded

StatusWhere the run is: queued, running, then succeeded, failed or cancelled. Refreshed every 5 s while it goes on. Docs ↗

DurationHow long the run took, from its start to its end, or to now while it goes on. Hover for the times.
31 s
CreatedWhen the run was queued: by the schedule, a sensor, a backfill, a fill or a person.
2026-11-08T15:45:25Z
StartedWhen its process started, once its turn in the queue came and its placement had room. Empty while it waits.
2026-11-08T19:26:04Z
EndedWhen it finished, whatever the outcome. Empty while it goes on.
2026-11-08T19:26:35Z
TriesTimes the run's process was started: 1 is normal; more means retries, a lost instance or a resume.
1

Partitions & triggerWhat this run does, and what made it start. Docs ↗

PartitionsThe partitions this run does (months, days, hours or named keys): each step runs once per partition. Docs ↗
brod4910/pmpp-mojo
TriggerWhat started it: the schedule, a sensor (with the snapshots it saw), a rebuild, a backfill, a fill, or manual (a person, or a binary's run command). Docs ↗
sensor of mojo.repos@8031460535849277283

CodeThe code this run ran, at the commit its binary was built from. Hover a name to see its source; click it to open the file on its host. Docs ↗

FunctionsThe pipeline, its steps in the order they run, and the dista tasks they fan out to, each linked to its line at the commit this run ran. Docs ↗
mojo_versions · versions · read_head_version
SourceThe commit its binary was built from (-D ORCA_COMMIT), in which repository, and the image it ran in, if any. Docs ↗
ac0c766d3f15 of https://github.com/magmalake/mojo-census
Driver logWhat the run's process printed: orca's lines and its steps' output, as the scheduler kept it. Each attempt under Steps has its own log too.
driver.log

Code hash 0x964a73bd21b8c449A hash of what the binary says about itself: its steps, partitions and schedule. It changes when they do, not on every build. Docs ↗

ResourcesWhat this run's own processes used: its process and the ones it started, dista's local workers too, measured by the scheduler or worker that started it. Not the rest of the machine: the machine's numbers, where they are recorded, are in their own card further down. With a request, what it asked for and was granted too. Docs ↗

Peak memoryThe most memory its processes held at once: the run's process and what it started (dista's local workers too), sampled every second by the scheduler or worker that started it, and at the end the largest single process. Not measured on EC2 or Kubernetes. Docs ↗
86 MB
CPU usedThe CPU time its processes used, user and system, and the most cores they kept busy over one sample's second. macOS gives only the time, and only for a process that made one attempt. Docs ↗
0.5 s, up to 0.1 cores at once

SettingsWhat the run was set up with, orca.toml and the flags applied: as its start recorded them, or else as the pipeline is registered. The pipeline's Config card says where each value came from. Docs ↗

As the pipeline is registered. Where each value came from

PlacedWhere it ran: local (beside the scheduler, on its machine), control (on the control host, within its limits), ec2 (instances of its own), or a remote worker's pool. Docs ↗
worker:bgent
Ran onThe remote worker that claimed and ran it, and its token. Docs ↗
bd410e935f57 (token 1, bgent)
Max runsThe most runs of this pipeline the scheduler starts at once (max_runs); the others wait in the queue.
1
SpotWhether its EC2 instances are Spot: cheaper, and AWS can take them back.
false
EnvironmentThe variables orca.toml's env and the flags set in the run's environment.
DISTA_WORKER_SLOTS=3

StepsEach step of each partition. Table: its status, attempts, times, what its latest attempt used, and its log. Timeline: the attempts on the clock, a row per step. Graph: the steps in the order they run, in this run's colours. Docs ↗succeeded

StepA step of the pipeline: a function that runs once per partition (mapped) or once over all of them (gather).PartitionThe partition this row is for; empty for a gather step, which runs once over all of them.StatusWhere it stands. Hover a status for what it means.AttemptsHow many times the step ran in this run: more than 1 means an attempt failed and it was retried.StartedWhen it started; empty while it waits.EndedWhen it finished, whatever the outcome.PeakThe most memory the step's latest attempt held at once; its page has each attempt's.CPUCPU used: for a step, its latest attempt's user and system seconds; for a machine, its busiest moment as a share of all cores.LogIts output: an attempt's, an instance's or the run's process's.ErrorWhy it failed, as the step or orca said.
versions pipelines/mojo_versions.mojo:53succeeded12026-11-08T19:26:06Z2026-11-08T19:26:34Z86 MB0.5 sattempt 1

Timeline

Open in Perfetto ↗timeline.json

The timeline loads as it comes into view.

ActionsWho did what to this run, from the UI or the orca command, as the user they logged in as.

AtWhen it happened, in UTC.ByThe user who did it, as they logged in.ActionWhat was done: the path of the action posted.FromWhere it came from.
2026-11-08T19:26:04Zworker:bgent/api/worker/claimworker

SnapshotsThe table snapshots each step read, and the ones it wrote (committed). A dataset's snapshot links to its lineage: upstream, what it was written from, and downstream, what was written from it. Docs ↗

StepA step of the pipeline: a function that runs once per partition (mapped) or once over all of them (gather).PartitionThe partition this row is for; empty for a gather step, which runs once over all of them.Read or wroteread: the step read this snapshot. wrote: it committed it, a new snapshot of the table.TableThe table's name in the warehouse.SnapshotA snapshot of a table: the table as one commit left it. Click for its lineage.
versionsreadmojo.repo_versions6434197257701166947
versionsreadmojo.repo_deps7899409276871555057
versionswrotemojo.repo_deps2370194890453897941
versionswrotemojo.repo_versions3070896634689552266