Skip to content

chore(ci): remove un-instantiated e2e.yml (0 jobs, permanently failing) - #19

Merged
hyperpolymath merged 1 commit into
mainfrom
chore/remove-uninstantiated-e2e
Jul 28, 2026
Merged

chore(ci): remove un-instantiated e2e.yml (0 jobs, permanently failing)#19
hyperpolymath merged 1 commit into
mainfrom
chore/remove-uninstantiated-e2e

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

This repos .github/workflows/e2e.ymlis an **un-instantiated scaffold**:jobs:is present but every job block is commented out. An emptyjobs:map is invalid, so the run dies with **0 jobs** andconclusion=failure— permanently, on every push touchingsrc/, ffi/ortests/**`.

It has never run a single test, so nothing is lost by removing it.

Why delete rather than instantiate: comparing git blob SHAs against a known-pure template clone shows this repos src/` is the RSR scaffold, differing in at most 4 files (largely just the repo name). There is no project-specific behaviour here to exercise end-to-end yet, and a job written anyway would pass without testing anything — a fake gate.

Debt recorded, not hidden: this repo has no E2E coverage. When real code lands, add a genuine E2E job and prove it can fail. The scaffold remains available in the template repo.

🤖 Generated with Claude Code

jobs: is present but every job block is commented out. An empty jobs: map is
invalid, so the run dies with 0 jobs and conclusion=failure on every push that
touches src/**, ffi/** or tests/**. It has never run a test.

Deleted rather than instantiated: blob-SHA comparison against a pure template
clone shows this repo's src/ differs from the scaffold in <=4 files, so there is
no project behaviour to exercise end-to-end. Writing a job anyway would pass
without testing anything -- a fake gate.

Debt: this repo has NO e2e coverage, and this file never provided any.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@gitar-bot

gitar-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
CI failed: CI failures caused by unapproved root entries (failing the root shape check) and K9 contract validation errors across jobs.

Overview

Analysis of 3 failed CI logs identified two primary issues: the repository's root shape check failed due to unallowed root files/directories (.githooks/, .hypatia-ignore, CLAUDE.md, flake.nix), and K9 contract validations failed due to missing magic numbers, signatures, and pedigree blocks.

Failures

Root Shape Check Failure (confidence: high)

  • Type: build
  • Affected jobs: 90322176296, 90322177126
  • Related to change: yes
  • Root cause: The script scripts/check-root-shape.sh detected new root entries that are missing from .machine_readable/root-allow.txt and also violated the estate-wide ban on Nix files (flake.nix).
  • Suggested fix: Remove the banned flake.nix file and add the remaining new root entries to .machine_readable/root-allow.txt, or move them to appropriate subdirectories.

K9 Contract Validation Failure (confidence: high)

  • Type: build
  • Affected jobs: 90322177700
  • Related to change: yes
  • Root cause: K9 configuration files failed validation checks due to missing 'K9!' magic numbers, missing signatures, and incomplete pedigree blocks.
  • Suggested fix: Update the K9 contract files to include the required magic numbers, signatures, and pedigree metadata blocks as required by the validator.

Summary

  • Change-related failures: 3 failures related to unauthorized root entries/Nix files and invalid K9 contracts.
  • Infrastructure/flaky failures: None.
  • Recommended action: Remove/migrate flake.nix, update .machine_readable/root-allow.txt for the new root files, and fix the K9 contract validation errors.
Code Review ✅ Approved

Removes the un-instantiated and permanently failing e2e.yml CI workflow file. No issues found.

Auto-approved and auto-merge armed: No blocking issues found.
Please see Auto-approve Docs for details on setting custom approval criteria. — merges when pipeline and required approvals pass.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

@gitar-bot
gitar-bot Bot enabled auto-merge (squash) July 28, 2026 15:25

@gitar-bot gitar-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gitar has auto-approved this PR and enabled auto-merge (configure)

@gitar-bot gitar-bot Bot added the gitar-approved Added by Gitar label Jul 28, 2026
@hyperpolymath
hyperpolymath disabled auto-merge July 28, 2026 15:28
@hyperpolymath
hyperpolymath merged commit 6661fe3 into main Jul 28, 2026
40 of 45 checks passed
@hyperpolymath
hyperpolymath deleted the chore/remove-uninstantiated-e2e branch July 28, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gitar-approved Added by Gitar

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant