Diagnostics¶

Logs and diagnostic output for a build.

DEBUG¶

string · default: no

The umbrella verbosity switch. DEBUG=yes forces on both SHOW_LOG (stream every command live) and SHOW_DEBUG (debug-level messages and extra state dumps) — the quickest way to get maximum visibility when diagnosing a build. See those two switches for what each turns on.

Bash
./compile.sh build BOARD=... BRANCH=... DEBUG=yes

SHARE_LOG¶

string

yes
no (default)

At the end of the build the framework assembles the whole run into a single ANSI log file; with SHARE_LOG=yes it uploads that file to Armbian’s paste servers — trying paste.armbian.com and its mirrors in turn until one succeeds — and prints the resulting share URL (also exposed as a logs_url output under GitHub Actions). It defaults to no because uploading is a network action and the log embeds local paths and environment details, so when left off the build instead prints the ready-made curl commands to upload it yourself. Turn it on when reporting a build issue, so maintainers can open the complete log from the link.

Bash
./compile.sh SHARE_LOG=yes

SHOW_LOG¶

string · default: yes when attached to a terminal

Streams the output of every command to the terminal as the build runs, prefixed and interleaved with the high-level progress messages, instead of quietly capturing it into the per-section files under output/logs. It defaults to yes whenever stdout is a terminal (and is also forced on under CI and when DEBUG=yes), on the assumption that an interactive user wants to watch the build; with it off you get only the concise section markers, and the captured output is surfaced only if a command fails. Set it to no for a cleaner console — the full logs are still written to disk either way — or yes to force live streaming when output is being redirected to a file or pipe.

SHOW_DEBUG¶

string · default: no

Raises the verbosity of the build to debug level: it lets the many debug-severity display_alert messages through, triggers extra state and variable dumps throughout the pipeline, un-quiets apt inside the chroot (dropping its -qq flag so package Conf/Inst lines appear), and bumps the log level of the Python configuration-aggregation helpers. It defaults to no to keep the log readable and focused on the high-level flow, and is automatically turned on when DEBUG=yes. Enable it when you are diagnosing the build framework itself and need to see exactly what each step is doing.

RAW_LOG¶

string · default: no

With RAW_LOG=yes the framework also keeps the uncompressed raw logs and bundles them into a *.raw.tar under output/logs, alongside the usual ANSI / ASCII / Markdown logs. Useful when you need the unprocessed output for deeper analysis.