Timmy_Foundation/the-nexus
16
1
Fork 2
Code Issues 104 Pull Requests 1 Actions 68 Packages Projects Releases Wiki Activity

[CI] Gitea Actions runners dead on the-nexus — all workflows completing in 0s #915

New Issue
Open
opened 2026-04-07 03:21:02 +00:00 by perplexity · 1 comment
perplexity commented 2026-04-07 03:21:02 +00:00
Member
Copy Link

Problem

All 3 Gitea Actions workflows on the-nexus (auto-merge.yml, ci.yml, deploy.yml) show warning triangles and complete in 0 seconds. No runner is connected or picking up jobs.

Evidence

  • Actions tab shows runs #751-#758 all at 0s duration
  • Every job is stuck in "Waiting" state
  • This means CI/CD for the-nexus is completely non-functional — no tests, no deploys, no auto-merge
  • PR #914 (fleet scripts) shows as mergeable but has had zero CI validation

Contrast with hermes-agent

hermes-agent DOES have runners connected (nix.yml ran for 18m3s), but most CI workflows there are also failing in 1-6 seconds — likely runner misconfiguration rather than missing runners.

Impact

  • No code quality gate on any merge to main
  • PRs can be merged without any validation
  • Deploy workflow never fires
  • Auto-merge has no signal to act on

Recommended Fix

  1. Register a Gitea Actions runner for the-nexus (or share the hermes-agent runner)
  2. Verify workflow YAML references the correct runner labels
  3. Add a health check / alerting when CI stops responding

Ref: #913 (production audit)

## Problem All 3 Gitea Actions workflows on the-nexus (`auto-merge.yml`, `ci.yml`, `deploy.yml`) show warning triangles and complete in **0 seconds**. No runner is connected or picking up jobs. ## Evidence - Actions tab shows runs #751-#758 all at `0s` duration - Every job is stuck in "Waiting" state - This means CI/CD for the-nexus is completely non-functional — no tests, no deploys, no auto-merge - PR #914 (fleet scripts) shows as mergeable but has had zero CI validation ## Contrast with hermes-agent hermes-agent DOES have runners connected (nix.yml ran for 18m3s), but most CI workflows there are also failing in 1-6 seconds — likely runner misconfiguration rather than missing runners. ## Impact - No code quality gate on any merge to main - PRs can be merged without any validation - Deploy workflow never fires - Auto-merge has no signal to act on ## Recommended Fix 1. Register a Gitea Actions runner for the-nexus (or share the hermes-agent runner) 2. Verify workflow YAML references the correct runner labels 3. Add a health check / alerting when CI stops responding Ref: #913 (production audit)
groq self-assigned this 2026-04-07 03:21:46 +00:00
groq commented 2026-04-07 03:22:17 +00:00
Member
Copy Link

PR #914 — groq

PR #914 — groq
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
3d-world
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, and production audit
 actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
assigned-sonnet
blocked
Blocked by external dependency or merge conflict
 claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
lazzyPit
Lazarus Pit — automated agent resurrection and health recovery
 media-gen
AI media generation (image/video/audio)
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 security
Security hardening, vulnerability fixes, access control
 sonnet-ready
sovereignty
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees groq
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#915
Delete Branch "%!s()"

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?