[llvm] [docs] Fix two stale file paths (PR #213994)

Hüseyin Kutsi Balcı via llvm-commits llvm-commits at lists.llvm.org
Wed Sep 9 02:26:27 PDT 2026


kutsibalci wrote:

Five workflows reported failures against this PR on 3 September. They are not what they look like,
so I would rather flag it than let anyone spend time on them.

They are the **original runs from 4 August**, resolved a month later without ever executing:

| | |
|---|---|
| `created_at` | `2026-08-04T16:20:08Z` |
| `updated_at` | `2026-09-03T16:22` |
| jobs, `total_count` | **0** — no job ever ran |
| head SHA | `4eda7034` |

`4eda7034` is the first version of this branch, from before the author-email fix. It has not been the
head of this PR for a month — the head is `5368a3eb`. That is also why *"Check for private emails
used in PRs"* is among the five: it is reporting on the commit that carried the noreply address,
which is precisely the commit that was replaced.

The runs that would actually mean something — the ones queued against `5368a3eb` when I rebased on
26 August — are still sitting at `action_required`. The rebase re-armed the approval gate and it has
not been released since. **So this PR has no CI result at all, rather than a bad one.**

Re-verified against today's `main` (`cd2f66534`) before posting, so this is not a stale claim:

| File | Says | Should say |
|---|---|---|
| `llvm/docs/HowToSubmitABug.rst:81` | `clang/utils/creduce-clang-crash.py` | `clang/utils/reduce-clang-crash.py` |
| `llvm/docs/PDB/PdbStream.md:142` | `llvm/DebugInfo/CodeView/CVDebugRecord.h` | `llvm/include/llvm/Object/CVDebugRecord.h` |

Both stale paths are still present, and both replacement paths exist in the tree.

@boomanaiden154 — you looked at this in August, and the email point you raised is resolved. Whenever
you have a moment for the button; or tell me it is not worth the CI minutes and I will close it.
Either is better than leaving it under five red checks that never ran.

*AI Tool Use Policy note: AI-assisted (Claude Code); the disclosure in the description covers the
change itself. The run metadata and the two paths above were checked against the API and today's
`main` before posting.*


https://github.com/llvm/llvm-project/pull/213994


More information about the llvm-commits mailing list