orcaLog in

Runs · mojo_activity · ·

Run 4763 cancelled

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

CreatedWhen the run was queued: by the schedule, a sensor, a backfill, a fill or a person.
2026-11-08T14:52:54Z
StartedWhen its process started, once its turn in the queue came and its placement had room. Empty while it waits.
EndedWhen it finished, whatever the outcome. Empty while it goes on.
2026-11-08T17:57:19Z
TriesTimes the run's process was started: 1 is normal; more means retries, a lost instance or a resume.
0
what hasn't succeeded

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 ↗
2025-12-26
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 gharchive.releases@4435771849334596760, gharchive.repo_hour@8194849994152763031

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 ↗

No links to the code: the binary records no source, or orca locate didn't map it.

Code hash 0x847d6f4604e8f29A 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 ↗
not measured
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 ↗
not measured

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

Max runsThe most runs of this pipeline the scheduler starts at once (max_runs); the others wait in the queue.
1
PlacementWhere its runs start (placement): default (the scheduler's runner), control, ec2, or a remote worker's pool.
worker:bgent
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 ↗cancelled

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.