issues

kci-dev results issues — KCIDB Issue Fetcher

Fetch KernelCI Database (KCIDB) issues associated with builds and boots, and new issues (first‑time observations) for a specific checkout.

Synopsis

kci-dev results issues [--builds | --boots | --new]
                       [--days <N>] [--arch <ARCH>] [--origin <ORIGIN>] [--latest]
                       [--giturl <URL> --branch <BRANCH> --commit <COMMIT>]
                       [--git-folder <PATH>]

Use one operating mode at a time: --builds, --boots, or --new.

Description

• Build/boot issue fetch: Retrieve KCIDB issues linked to a specific build/boot or across all available trees on the dashboard.
• New‑issue detection: Identify issues observed for the first time for a checkout (defined by --giturl/--branch/--commit, or discovered via --git-folder).
• Scope control: Restrict queries by architecture, time window, result recency, and data origin. Default origin is maestro.

Common Workflows

Detect build issues

kci-dev results issues --builds

Detect build issues across all checkouts (recent window)

kci-dev results issues --builds --days 7 --origin maestro

Detect failed/incomplete boot without any issue associated to them

kci-dev results issues --missing --boots

Detect new issues for a checkout (dashboard scan)

kci-dev results issues --new --days 7 --origin maestro

Detect new issues for an explicit checkout (git tuple)

kci-dev results issues --new \
  --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git \
  --branch main \
  --commit v6.12 \
  --origin maestro

Filter to a specific architecture and pick the latest available results

kci-dev results issues --builds --arch arm64 --days 3 --latest

The examples above mirror the CLI help and show the intended combinations.

Options

Mode & Targets

• --builds Fetch KCIDB issues for builds.
• --boots Fetch KCIDB issues for boots.
• --new Detect new KCIDB issues (first‑time observations) for a checkout.

Dashboard Scope

• --days <N> (int, default: 7) Time window (in days) to consider when scanning dashboard results.
• --origin <ORIGIN> (default: maestro) KCIDB origin to query.
• --arch <ARCH> Filter results by architecture (e.g., arm64, x86_64).
• --latest Select the latest results available within the query.

Checkout Specification (for --new)

Provide the checkout explicitly or let the tool infer it from a local repo.

• --giturl <URL> Git URL of the kernel tree.
• --branch <BRANCH> Branch to evaluate.
• --commit <COMMIT> Commit SHA or tag (e.g., v6.12).
• --git-folder <PATH> Path to a local git repository. Must exist and be a directory. When provided, the tool may derive giturl/branch/commit from the local checkout.

Examples (from CLI help)

# Detect build issues
kci-dev results issues --builds
kci-dev results issues --builds --days <number-of-days> --origin <origin>

# Detect boot issues
kci-dev results issues --boots
kci-dev results issues --boots --days <number-of-days> --origin <origin>

# Detect new issues for a checkout
kci-dev results issues --new --days <number-of-days> --origin <origin>
kci-dev results issues --new --giturl <git-url> --branch <git-branch> --commit <commit> --origin <origin>

Troubleshooting

• No results: Check your --days window, --origin, and that the target builds/boots are failed or inconclusive.
• Checkout not resolved: When using --new, ensure the --giturl/--branch/--commit tuple is provided, or pass --git-folder that points to a valid git repo.
• Architecture filter too narrow: Try removing --arch or broadening it.