Docs: the CI failure nobody can read the logs for, and how the library is built #1177
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1177
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/known-ci-issue"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two pages, both about the parts of this project that fail silently.
docs/CI.md→ "Known issue: some pushes create no workflow runs at all"Since ~01:30 today, pull requests I open and merges I push produce no run and no task row — not queued, not failed, nothing — while another writer on the same repository, account and two-runner host dispatches normally. Each wrong hypothesis cost an iteration, so the page records them:
if:guardheadformatThat last row is the useful one: it is every event from this credential, not a pull-request quirk. Two suspects remain, both server-side — token-pushed commits being skipped to avoid recursion, or a repo/user setting suppressing this actor.
The page ends with the one check a person can do in a browser: no run row = the event created nothing; a run row stuck at
waiting= runner labels are wrong. Those are different bugs and the API cannot tell them apart — which is exactly why the failure had to be written down somewhere findable.docs/MAINTAINING.mdThe intake pipeline the catalogue work actually follows: request → spec → importer → suite → closing comment; a source-reliability table (rendered spec page > datasheet text layer > wiki table > reseller listing); the five extraction scripts and what each pulls; the rules the importer and suite enforce; and what to do when a vendor is hard. It names this project's own scars — the 25 MB PDF cache that had to be amended out, the PoE suffix that doesn't mean every port, the family-wide range that must stay out of the catalogue rather than be averaged.
Linked from CONTRIBUTING. Suite: 114 suites, 5311 assertions, 0 failed.
The auto-rebase job failed. This is a problem with the automation, not with this change.
The run is at the Actions tab. Nothing was pushed, so the branch is exactly as you wrote it.