orcaLog in

Runs · gharchive · ·

Run 278 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.
54 s
CreatedWhen the run was queued: by the schedule, a sensor, a backfill, a fill or a person.
2026-11-07T04:31:10Z
StartedWhen its process started, once its turn in the queue came and its placement had room. Empty while it waits.
2026-11-07T04:31:10Z
EndedWhen it finished, whatever the outcome. Empty while it goes on.
2026-11-07T04:32:03Z
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 ↗
2026-08-17
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 ↗
fill

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 ↗
gharchive · load_day · index_hour · hour_task · merge_repo_hour
SourceThe commit its binary was built from (-D ORCA_COMMIT), in which repository, and the image it ran in, if any. Docs ↗
47fea9378b0d 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 0xe6cdc4870d3f3535A 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

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 ↗
local
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=2
GHARCHIVE_EVENTS=off
GHARCHIVE_PARALLEL=2

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

MachinesSamples of the whole machine, every few seconds while the run ran (ORCA_SAMPLE_SECONDS, 5 by default): its CPU, memory, fullest disk, disk io and network, by a sampler the runner starts beside the run's process. They count everything on that machine, not just this run. What the run's own processes used is in Resources, above. The steps lane lines a busy stretch up with the step it came from. A run on a remote worker has none: the worker measures only its processes. Docs ↗

The whole machine, while this run ran: the scheduler's machine (the local runner). Not this run's own use; that is in Resources.

A shared machine: 1 other run ran on it at the same time, so these numbers are theirs too.

user + system iowait steal memory fullest disk disk io network warning

0s10s20s30s40s50sload_dayload_day 2026-08-17 succeeded: 53slocalcpu 46%mem 14% · disk 11%io · net 21 MB/s
InstanceWhere the samples were taken: local (the scheduler's machine), control, an EC2 head or worker, or a pod.SamplesHow many samples the sampler took.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.Busiest coreThe busiest single core's use at its highest.StealCPU time the hypervisor gave to other machines.MemoryMemory used at its highest, of the machine's total.DiskThe fullest disk the run writes to, at its fullest.Disk ioDisk reads and writes, at their highest rate.NetworkNetwork traffic in and out, at its highest rate.WarningsStretches with memory or a disk over 90%, or CPU steal over 20%: what slows or fails most runs.
local1246%54%0%1.2 GB of 8.1 GB (14%)8.5 GB of 80 GB (11%)286 kB/s21 MB/s

Timeline

The timeline loads as it comes into view.

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.
load_day2026-08-17wrotegharchive.events6506015240750152958
load_day2026-08-17wrotegharchive.events2727296400007978375
load_day2026-08-17wrotegharchive.events4939050704098312326
load_day2026-08-17wrotegharchive.events8796656864082067092
load_day2026-08-17wrotegharchive.events8657793983038746063
load_day2026-08-17wrotegharchive.events1666427251588314353
load_day2026-08-17wrotegharchive.events9030127174641440906
load_day2026-08-17wrotegharchive.events4808837894652005634
load_day2026-08-17wrotegharchive.events3260827820251890443
load_day2026-08-17wrotegharchive.events8615593772632741252
load_day2026-08-17wrotegharchive.events6851430082184905649
load_day2026-08-17wrotegharchive.events157155199015066351
load_day2026-08-17wrotegharchive.events717179477837672653
load_day2026-08-17wrotegharchive.events6902166270285543251
load_day2026-08-17wrotegharchive.events6787026827411930294
load_day2026-08-17wrotegharchive.events2515784183666562510
load_day2026-08-17wrotegharchive.events8529432162996020772
load_day2026-08-17wrotegharchive.events19316586091233410
load_day2026-08-17wrotegharchive.events5798395014139757005
load_day2026-08-17wrotegharchive.events3318519738817212160
load_day2026-08-17wrotegharchive.events7223434179724759472
load_day2026-08-17wrotegharchive.events3216446888932061041
load_day2026-08-17wrotegharchive.events5651401806655946553
load_day2026-08-17wrotegharchive.events1167996522740978897
load_day2026-08-17wrotegharchive.candidates930239223932500358
load_day2026-08-17wrotegharchive.repo_hour7336797151270908377
load_day2026-08-17wrotegharchive.releases2360254448906116028