Project Bluefin

Operating System Factory

Community Driven Development and Testing

Updated Aug 13, 2026, 11:45 PM UTCSource: projectbluefin core metrics & feedsSnapshot: degradedRaw dataset ↗

Is the last release good?

Per-lane verdict under ADR 0002: publishing build + lab QA on the exact digest + cosign signature. Security regression shown alongside, never gating. Collected Aug 19, 2026, 6:11 PM UTC.

bluefin-stable

bad
build: failedQA (lab): pendingsignature: passedCVE regression: unavailable
sha256:383f523982a8…build run ↗
gate QA evidence pending for suite(s): smoke against digest sha256:383f5

bluefin-testing

bad
build: failedQA (lab): pendingsignature: passedCVE regression: unavailable
sha256:bf615b200fae…build run ↗
gate QA evidence pending for suite(s): smoke, system against digest sha256:bf615

bluefin-lts-stable

bad
build: passedQA (lab): failedsignature: passedCVE regression: unavailable
sha256:727e3f36eede…build run ↗

bluefin-lts-testing

bad
build: passedQA (lab): failedsignature: passedCVE regression: unavailable
sha256:345decb822bb…build run ↗

dakota-testing

pending
build: passedQA (lab): pendingsignature: passedCVE regression: unavailable
sha256:ae5bda007a78…build run ↗
gate QA evidence pending for suite(s): system against digest sha256:ae5bd

Rolling 7-day factory build health

All factory publish builds in the rolling UTC window. Release verdict cards above remain a separate per-lane digest, QA, and signature judgment.

All factory builds32completed publish builds
Passed25terminal publish outcomes
Failed7terminal publish outcomes
Success rate78%passed / completed
Duration50mmedian · 64m average
Running work0separate in-progress signal

Source: data/history/build-runs.ndjson · plane: publish · terminal statuses: passed/failed · UTC rolling window. GitHub Actions publish builds are authoritative here; Argo Workflows lab runs remain separate. Running work is shown separately when published by the history collector. Missing history renders Build health unavailable with its state_reason.

What's degrading?

failingbluefin-stable release is bad
degradingbluefin-stable QA evidence stale
gate QA evidence pending for suite(s): smoke against digest sha256:383f5
failingbluefin-testing release is bad
degradingbluefin-testing QA evidence stale
gate QA evidence pending for suite(s): smoke, system against digest sha256:bf615
failingbluefin-lts-stable release is bad
failingbluefin-lts-testing release is bad
degradingdakota-testing QA evidence stale
gate QA evidence pending for suite(s): system against digest sha256:ae5bd
degradingbluefin:stable build duration trending up
recent runs average 36m vs 25m before (+47%)
degradingbluefin:testing build duration trending up
recent runs average 38m vs 18m before (+115%)
failingbluefin:testing publishing builds failing
degradingbluefin-lts:stable build duration trending up
recent runs average 15m vs 11m before (+42%)
degradingbluefin:testing release freshness

Image status

Days since latest published release in each lane, sourced from each repo's GitHub Releases feed.

Bluefin LTS

Releases →
—testingAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.
Tests:devsmokesoftsys
—stableAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.
Tests:smoke

Aurora

Releases →
—testingAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.
Tests:commondevflatcarsmokesoftsys
—stableAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.

Bazzite

Releases →
—testingAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.
Tests:commondevflatcarsmokesoftsys
—stableAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.

Dakota

Releases →
—testingAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.
Tests:devsmokesoftsys

COSMIC

Releases →
—stableAwaiting Evidence
COSMIC image is built in-cluster via the cosmic-build-pipeline Argo WorkflowTemplate and exported to the local Zot registry — no external GitHub release timestamp is collected yet.
—nvidiaAwaiting Evidence
COSMIC image is built in-cluster via the cosmic-build-pipeline Argo WorkflowTemplate and exported to the local Zot registry — no external GitHub release timestamp is collected yet.

Zirconium

Releases →
—latestAwaiting Evidence
No published release timestamp is present in docs/data/factory-stats.json for this lane.

GNOME OS

—nightlyAwaiting Evidence
Known GNOME OS workflow exists, but no repo-owned artifact publishes a nightly release timestamp yet.

Fedora bootc

Releases →
—stableAwaiting Evidence
Known Fedora bootc poller exists, but no repo-owned artifact publishes a stable release timestamp yet.
—testingAwaiting Evidence
Known Fedora bootc poller exists, but no repo-owned artifact publishes a testing release timestamp yet.
Tests:commondevflatcarsmokesoftsys

Contributor Clusters

Who's donating cycles to test Bluefin right now — each card is a real machine running real tests.

exo-0

Ready
worker
Fedora CoreOS 44.20260707.3.1
Mem use
29.4%
CPU use
1.8%
Capacity: 32 threads · 62 GiB
Specs: Dedicated worker host (16c/32t) · Headless console
IP: 192.168.1.170
Always-on dedicated worker node. Schedules KubeVirt virt-launcher test VMs and system-upgrade controllers.
ghost40G

ghost

Ready
control-plane
Bluefin (Version: testing-44.20260708.3)
Mem use
16.5%
CPU use
3.7%
Capacity: 32 threads · 63 GiB
Specs: Ryzen AI MAX+ 395 (16c/32t) · RDNA 3.5 (gfx1151) · ROCm AMDGPU enabled
IP: 192.168.1.102
Control-plane + KubeVirt compute host. Pinned for local Qwen3.6 LLM inference and ARC runners.
exo-040G

BuildStream Cache Utilization

Remote-execution cache fill across both cache drives: ghost (bazel-remote + Buildbarn shard) and exo-0 (Buildbarn shard).

bst Cache Heat Map

live
Collected: Aug 19, 2026, 6:11 PM UTC

bazel-remote is nodeSelector-pinned to ghost; Buildbarn's 2-shard CAS/AC is scheduled across ghost and exo-0 via podAntiAffinity. Buildbarn's block-device-backed storage is preallocated on disk, so its cell values are a derived estimate of logical fill (allocator counters × known block size), not raw disk bytes.

Heatmap scale: Cache utilization (%) from 0% to 100%; gray cells are unavailable.

Cache heat trend

USB-4 Distributed Build System

Link DOWN · 40 Gbps
Point-to-point link: ghost ↔ exo-0
40 Gbps Thunderbolt Link
40Gbps
Latency: ms
ghost link: unavailable · exo-0 link: unavailable
Work Distribution
ghost: 45%exo-0: 55%
Distributed RE build action scheduling ratio
Cold vs Warm Speedup
4.2xspeedup
Cold: 20.2m→Warm: 4.8m
Layer Rechunking Speed
145s
Fast re-chunking over high-throughput USB-4 CAS sync

Recent Runs & Builds

faildakota:latest
Aug 1, 2026, 3:47 PM UTC
Duration: 0m · Trigger: manual
passedpr-label-poller-1785599100
Aug 1, 2026, 3:45 PM UTC
Duration: 1m · Trigger: manual
failcosmic-commit-poller-1785599040
Aug 1, 2026, 3:44 PM UTC
Duration: 0m · Trigger: manual
passedbluefin:rawhide
Aug 1, 2026, 3:42 PM UTC
Duration: 2m · Trigger: poller
passedpr-label-poller-1785598800
Aug 1, 2026, 3:40 PM UTC
Duration: 1m · Trigger: manual
faildakota:7eab3cc0e7934e0041ec33e962134f74450e9c25
Aug 1, 2026, 3:35 PM UTC
Duration: 1m · Trigger: pr-poller
passedpr-label-poller-1785598500
Aug 1, 2026, 3:35 PM UTC
Duration: 1m · Trigger: manual
runningbluefin:testing
Aug 1, 2026, 3:30 PM UTC
Duration: 18m · Trigger: pr-poller
runningsnosi:latest
Aug 1, 2026, 3:30 PM UTC
Duration: 18m · Trigger: poller
passedorphan-vm-cleanup-1785598200
Aug 1, 2026, 3:30 PM UTC
Duration: 0m · Trigger: manual
passedorphan-pod-gc-1785598200
Aug 1, 2026, 3:30 PM UTC
Duration: 0m · Trigger: manual
runningaurora:stable
Aug 1, 2026, 3:27 PM UTC
Duration: 21m · Trigger: poller

Open Bugs (1)

#552: test: align Dakota upstream availability fixture
Created: Aug 1, 2026, 5:38 PM UTC

Data source: factory-stats.json · updated Aug 13, 2026, 11:45 PM UTC