|
| 1 | ++++ |
| 2 | +title = 'issues' |
| 3 | +date = 2025-11-13T17:37:07+09:00 |
| 4 | +description = 'Fetch KernelCI Database (KCIDB) issues associated with **builds** and **boots**, and **new issues** (first‑time observations) for a specific checkout.' |
| 5 | ++++ |
| 6 | + |
| 7 | +# `kci-dev results issues` — KCIDB Issue Fetcher |
| 8 | + |
| 9 | +Fetch KernelCI Database (KCIDB) issues associated with **builds** and **boots**, and **new issues** (first‑time observations) for a specific checkout. |
| 10 | + |
| 11 | +--- |
| 12 | + |
| 13 | +## Synopsis |
| 14 | + |
| 15 | +```bash |
| 16 | +kci-dev results issues [--builds | --boots | --new] |
| 17 | + [--days <N>] [--arch <ARCH>] [--origin <ORIGIN>] [--latest] |
| 18 | + [--giturl <URL> --branch <BRANCH> --commit <COMMIT>] |
| 19 | + [--git-folder <PATH>] |
| 20 | +``` |
| 21 | + |
| 22 | +> Use one operating mode at a time: `--builds`, `--boots`, or `--new`. |
| 23 | +
|
| 24 | +--- |
| 25 | + |
| 26 | +## Description |
| 27 | + |
| 28 | +* **Build/boot issue fetch**: Retrieve KCIDB issues linked to a specific build/boot or across *all available trees* on the dashboard. |
| 29 | +* **New‑issue detection**: Identify issues **observed for the first time** for a checkout (defined by `--giturl/--branch/--commit`, or discovered via `--git-folder`). |
| 30 | +* **Scope control**: Restrict queries by architecture, time window, result recency, and data origin. Default origin is `maestro`. |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +## Common Workflows |
| 35 | + |
| 36 | +### Detect build issues |
| 37 | + |
| 38 | +```bash |
| 39 | +kci-dev results issues --builds |
| 40 | +``` |
| 41 | + |
| 42 | +### Detect build issues across all checkouts (recent window) |
| 43 | + |
| 44 | +```bash |
| 45 | +kci-dev results issues --builds --days 7 --origin maestro |
| 46 | +``` |
| 47 | + |
| 48 | +### Detect failed/incomplete boot without any issue associated to them |
| 49 | + |
| 50 | +```bash |
| 51 | +kci-dev results issues --missing --boots |
| 52 | +``` |
| 53 | + |
| 54 | +### Detect **new** issues for a checkout (dashboard scan) |
| 55 | + |
| 56 | +```bash |
| 57 | +kci-dev results issues --new --days 7 --origin maestro |
| 58 | +``` |
| 59 | + |
| 60 | +### Detect **new** issues for an explicit checkout (git tuple) |
| 61 | + |
| 62 | +```bash |
| 63 | +kci-dev results issues --new \ |
| 64 | + --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git \ |
| 65 | + --branch main \ |
| 66 | + --commit v6.12 \ |
| 67 | + --origin maestro |
| 68 | +``` |
| 69 | + |
| 70 | +### Filter to a specific architecture and pick the latest available results |
| 71 | + |
| 72 | +```bash |
| 73 | +kci-dev results issues --builds --arch arm64 --days 3 --latest |
| 74 | +``` |
| 75 | + |
| 76 | +> The examples above mirror the CLI help and show the intended combinations. |
| 77 | +
|
| 78 | +--- |
| 79 | + |
| 80 | +## Options |
| 81 | + |
| 82 | +### Mode & Targets |
| 83 | + |
| 84 | +* `--builds` |
| 85 | + Fetch KCIDB issues for **builds**. |
| 86 | +* `--boots` |
| 87 | + Fetch KCIDB issues for **boots**. |
| 88 | +* `--new` |
| 89 | + Detect **new** KCIDB issues (first‑time observations) for a checkout. |
| 90 | + |
| 91 | +### Dashboard Scope |
| 92 | + |
| 93 | +* `--days <N>` *(int, default: 7)* |
| 94 | + Time window (in days) to consider when scanning dashboard results. |
| 95 | +* `--origin <ORIGIN>` *(default: `maestro`)* |
| 96 | + KCIDB origin to query. |
| 97 | +* `--arch <ARCH>` |
| 98 | + Filter results by architecture (e.g., `arm64`, `x86_64`). |
| 99 | +* `--latest` |
| 100 | + Select the **latest** results available within the query. |
| 101 | + |
| 102 | +### Checkout Specification (for `--new`) |
| 103 | + |
| 104 | +Provide the checkout explicitly **or** let the tool infer it from a local repo. |
| 105 | + |
| 106 | +* `--giturl <URL>` |
| 107 | + Git URL of the kernel tree. |
| 108 | +* `--branch <BRANCH>` |
| 109 | + Branch to evaluate. |
| 110 | +* `--commit <COMMIT>` |
| 111 | + Commit SHA or tag (e.g., `v6.12`). |
| 112 | +* `--git-folder <PATH>` |
| 113 | + 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. |
| 114 | + |
| 115 | +--- |
| 116 | + |
| 117 | +## Examples (from CLI help) |
| 118 | + |
| 119 | +```bash |
| 120 | +# Detect build issues |
| 121 | +kci-dev results issues --builds |
| 122 | +kci-dev results issues --builds --days <number-of-days> --origin <origin> |
| 123 | + |
| 124 | +# Detect boot issues |
| 125 | +kci-dev results issues --boots |
| 126 | +kci-dev results issues --boots --days <number-of-days> --origin <origin> |
| 127 | + |
| 128 | +# Detect new issues for a checkout |
| 129 | +kci-dev results issues --new --days <number-of-days> --origin <origin> |
| 130 | +kci-dev results issues --new --giturl <git-url> --branch <git-branch> --commit <commit> --origin <origin> |
| 131 | +``` |
| 132 | + |
| 133 | +--- |
| 134 | + |
| 135 | +## Troubleshooting |
| 136 | + |
| 137 | +* **No results**: Check your `--days` window, `--origin`, and that the target builds/boots are *failed* or *inconclusive*. |
| 138 | +* **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. |
| 139 | +* **Architecture filter too narrow**: Try removing `--arch` or broadening it. |
| 140 | + |
| 141 | +--- |
0 commit comments