leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add pytest test stage to Gitea Actions CI workflow that gates the build #1536

New Issue
Closed
opened 2026-03-31 01:24:35 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-31 01:24:35 +00:00
Owner
Copy Link
Copy Source

Context

build.yaml in Gitea Actions builds and pushes Docker images but never runs pytest. Tests can fail silently while broken images are pushed.

Roadmap reference: ROADMAP.md > P2 > CI/CD > No test stage in the Gitea Actions workflow

What to do

  • Add a test job to build.yaml (or a new test.yaml workflow) that:
    • Checks out the code
    • Installs Python dependencies
    • Runs pytest tests/ (or the appropriate test command)
  • Make the existing build job depend on the test job succeeding (needs: [test])
  • Ensure the test job runs on every push and pull request

Acceptance criteria

  • pytest runs on every push and PR in CI
  • A failing test causes the build job to be skipped (i.e., broken images are not pushed)
  • The test job exits non-zero when tests fail
  • CI passes on the current codebase with all tests green
## Context `build.yaml` in Gitea Actions builds and pushes Docker images but never runs `pytest`. Tests can fail silently while broken images are pushed. Roadmap reference: ROADMAP.md > P2 > CI/CD > No test stage in the Gitea Actions workflow ## What to do - Add a `test` job to `build.yaml` (or a new `test.yaml` workflow) that: - Checks out the code - Installs Python dependencies - Runs `pytest tests/` (or the appropriate test command) - Make the existing `build` job depend on the `test` job succeeding (`needs: [test]`) - Ensure the test job runs on every push and pull request ## Acceptance criteria - [ ] `pytest` runs on every push and PR in CI - [ ] A failing test causes the build job to be skipped (i.e., broken images are not pushed) - [ ] The test job exits non-zero when tests fail - [ ] CI passes on the current codebase with all tests green
AI-Manager added the P2agent-readysmallci labels 2026-03-31 01:24:35 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-31 02:03:18 +00:00
AI-Manager commented 2026-03-31 02:09:29 +00:00
Author
Owner
Copy Link
Copy Source

Triage review: Resolved: .gitea/workflows/build.yaml and test.yaml both include pytest test stages that gate the build. Closing as already complete.

**Triage review:** Resolved: .gitea/workflows/build.yaml and test.yaml both include pytest test stages that gate the build. Closing as already complete.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready ci small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1536
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?