cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

test(e2e): workflow example 8 — cloud infrastructure management (supervised profile) #794

Closed
freemo wants to merge 1 commit from test/e2e-wf08-cloud-infra into master
pull from: test/e2e-wf08-cloud-infra
merge into: cleveragents:master
Conversation 6 Commits 1 Files changed 2 +684
freemo commented 2026-03-12 23:11:56 +00:00
Owner
Copy link

Summary

E2E Robot Framework test for Specification Workflow Example 8: Cloud Infrastructure Management using the supervised automation profile.

Exercises the complete WF8 scenario: a DevOps team uses CleverAgents to analyse Terraform-managed infrastructure, identify unused/over-provisioned resources, and generate cost-optimisation recommendations.

Closes #754

What Changed

  • New file: robot/e2e/wf08_cloud_infra.robot — full E2E test covering:
    • Custom resource type registration (local/terraform-state with copy_on_write sandbox) with output and error pattern verification
    • Custom skill creation (local/terraform-ops) with 3 tool references and skill composition via includes: [local/file-ops] (AC #3), with includes integration verified in output
    • Stub validation registration (local/tf-validate, local/tf-plan) using WF07's inline code: pattern, attached to the project (spec WF8 Step 2); tf-plan uses mode: informational per spec distinction from blocking tf-validate
    • Dynamic actor selection based on available API keys (Anthropic preferred, OpenAI fallback)
    • Action creation with 4 invariants and supervised automation profile, with output name verification
    • Resource registration for both git-checkout and the custom local/terraform-state type
    • Project creation linking both resources with project-level invariants
    • Full plan lifecycle: plan use → plan status (post-strategize) → plan execute (strategize) → plan execute (execute) → plan diff → plan lifecycle-apply --yes
    • Intermediate plan status check between strategize and execute phases (mirrors WF05 lifecycle pattern)
    • Supervised automation profile extraction and assertion (AC #5) using WF05's fallback-to-status pattern
    • Post-apply plan state verification via plan status --format json (phase + processing_state assertion)
    • Post-apply git commit verification using baseline SHA comparison (soft check per WF05 resilience pattern)
    • Diff content verification for meaningful infrastructure-related output
    • Infrastructure analysis output verification with two-tier keyword matching (broad + analysis-specific) and threshold ≥ 5 total / ≥ 2 analysis-specific; plan_result excluded from analysis to prevent tautological keyword satisfaction
    • Test-level [Teardown] with diagnostic plan status/tree logging on failure
    • [Timeout] 30 minutes on the test case
    • Traceback and INTERNAL error checks on stdout+stderr combined for all CLI commands (including validation attach)
    • --format json on registration commands (resource type, skill, action) and validation commands (add + attach) for consistency
    • Soft warning (WARN) if validation registration returns non-zero RC
    • timeout=60s on_timeout=kill on all git Run Process calls
    • Force Tags E2E at suite level (consistent with WF05/WF07/WF14)
    • Documented spec divergences for omitted --arg parameters on plan use
  • Updated file: CHANGELOG.md — added entry for WF08 E2E test

Design Decisions

  • Plan ID extraction: Uses --format json + Safe Parse Json Field (the m6 pattern) rather than ULID regex, for maximum reliability.
  • LLM resilience: All LLM-dependent commands use expected_rc=None with post-hoc IF rc != 0 → Fail pattern, plus Should Not Contain Traceback and INTERNAL on combined stdout+stderr.
  • Unique names: Resource and project names include a uuid4().hex[:12] suffix for parallel CI safety. Action, skill, and resource type names are static (safe due to per-suite DB isolation).
  • Graceful skip: Skip If No LLM Keys guard prevents hard failures in keyless CI environments.
  • copy_on_write vs filesystem_copy: Documented in a comment — the implementation maps both synonymously; the canonical enum variant is used.
  • Skill schema alignment: Tool references use SkillToolRefSchema-compatible format (namespaced names, no input_schema on refs). Spec divergences documented in comments.
  • Validation registration: Uses WF07's inline code: block pattern with stub validations that always pass, exercising the registration/attach path without requiring external terraform tooling. tf-plan uses mode: informational per spec WF8 Step 2 intent (advisory vs blocking).
  • Validation RC soft check: Both validation add commands log a WARN if rc != 0 — matches WF07 lenience pattern while providing diagnostic visibility.
  • Post-apply git verification: Uses baseline SHA comparison with soft check (WARN) rather than hard failure, matching WF05's resilience to non-deterministic LLM output.
  • plan lifecycle-apply: Uses the non-deprecated command, consistent with WF05, m2_acceptance, and m6_acceptance.
  • Keyword threshold: Two-tier approach — broad infrastructure terms + analysis-specific terms (cost, optimi, savings, right-siz, unused, over-provision, recommend) with ≥ 5 total and ≥ 2 analysis-specific. provision removed from list to avoid double-counting with over-provision. plan_result excluded from collected output to prevent action metadata from trivially satisfying thresholds.
  • Intermediate status check: plan status check added between strategize and execute phases for stronger lifecycle validation, mirroring WF05 pattern.
  • Spec divergences: Documented via inline comments for each adaptation (resource_kind vs physical, includes vs include_skills, namespaced tool names, invariant count differences, omitted --arg parameters).

Quality Gates

Gate Status
nox -e lint ✅ Pass
nox -e typecheck ✅ Pass (0 errors)
nox -e unit_tests ✅ Pass (480 features, 12565 scenarios)
nox -e integration_tests ✅ Pass (1775/1775)
nox -e e2e_tests ✅ Pass (56/56, including WF08)
nox -e coverage_report ✅ Pass (98% ≥ 97%)
## Summary E2E Robot Framework test for **Specification Workflow Example 8: Cloud Infrastructure Management** using the `supervised` automation profile. Exercises the complete WF8 scenario: a DevOps team uses CleverAgents to analyse Terraform-managed infrastructure, identify unused/over-provisioned resources, and generate cost-optimisation recommendations. Closes #754 ## What Changed - **New file:** `robot/e2e/wf08_cloud_infra.robot` — full E2E test covering: - Custom resource type registration (`local/terraform-state` with `copy_on_write` sandbox) with output and error pattern verification - Custom skill creation (`local/terraform-ops`) with 3 tool references and skill composition via `includes: [local/file-ops]` (AC #3), with `includes` integration verified in output - Stub validation registration (`local/tf-validate`, `local/tf-plan`) using WF07's inline `code:` pattern, attached to the project (spec WF8 Step 2); `tf-plan` uses `mode: informational` per spec distinction from blocking `tf-validate` - Dynamic actor selection based on available API keys (Anthropic preferred, OpenAI fallback) - Action creation with 4 invariants and `supervised` automation profile, with output name verification - Resource registration for both `git-checkout` and the custom `local/terraform-state` type - Project creation linking both resources with project-level invariants - Full plan lifecycle: `plan use` → `plan status` (post-strategize) → `plan execute` (strategize) → `plan execute` (execute) → `plan diff` → `plan lifecycle-apply --yes` - Intermediate `plan status` check between strategize and execute phases (mirrors WF05 lifecycle pattern) - Supervised automation profile extraction and assertion (AC #5) using WF05's fallback-to-status pattern - Post-apply plan state verification via `plan status --format json` (phase + processing_state assertion) - Post-apply git commit verification using baseline SHA comparison (soft check per WF05 resilience pattern) - Diff content verification for meaningful infrastructure-related output - Infrastructure analysis output verification with two-tier keyword matching (broad + analysis-specific) and threshold ≥ 5 total / ≥ 2 analysis-specific; `plan_result` excluded from analysis to prevent tautological keyword satisfaction - Test-level `[Teardown]` with diagnostic plan status/tree logging on failure - `[Timeout] 30 minutes` on the test case - Traceback and INTERNAL error checks on `stdout+stderr` combined for **all** CLI commands (including validation attach) - `--format json` on registration commands (resource type, skill, action) **and** validation commands (add + attach) for consistency - Soft warning (WARN) if validation registration returns non-zero RC - `timeout=60s on_timeout=kill` on all git `Run Process` calls - `Force Tags E2E` at suite level (consistent with WF05/WF07/WF14) - Documented spec divergences for omitted `--arg` parameters on `plan use` - **Updated file:** `CHANGELOG.md` — added entry for WF08 E2E test ## Design Decisions - **Plan ID extraction:** Uses `--format json` + `Safe Parse Json Field` (the m6 pattern) rather than ULID regex, for maximum reliability. - **LLM resilience:** All LLM-dependent commands use `expected_rc=None` with post-hoc `IF rc != 0 → Fail` pattern, plus `Should Not Contain Traceback` and `INTERNAL` on combined stdout+stderr. - **Unique names:** Resource and project names include a `uuid4().hex[:12]` suffix for parallel CI safety. Action, skill, and resource type names are static (safe due to per-suite DB isolation). - **Graceful skip:** `Skip If No LLM Keys` guard prevents hard failures in keyless CI environments. - **`copy_on_write` vs `filesystem_copy`:** Documented in a comment — the implementation maps both synonymously; the canonical enum variant is used. - **Skill schema alignment:** Tool references use `SkillToolRefSchema`-compatible format (namespaced names, no `input_schema` on refs). Spec divergences documented in comments. - **Validation registration:** Uses WF07's inline `code:` block pattern with stub validations that always pass, exercising the registration/attach path without requiring external terraform tooling. `tf-plan` uses `mode: informational` per spec WF8 Step 2 intent (advisory vs blocking). - **Validation RC soft check:** Both `validation add` commands log a WARN if `rc != 0` — matches WF07 lenience pattern while providing diagnostic visibility. - **Post-apply git verification:** Uses baseline SHA comparison with soft check (WARN) rather than hard failure, matching WF05's resilience to non-deterministic LLM output. - **`plan lifecycle-apply`:** Uses the non-deprecated command, consistent with WF05, m2_acceptance, and m6_acceptance. - **Keyword threshold:** Two-tier approach — broad infrastructure terms + analysis-specific terms (cost, optimi, savings, right-siz, unused, over-provision, recommend) with ≥ 5 total and ≥ 2 analysis-specific. `provision` removed from list to avoid double-counting with `over-provision`. `plan_result` excluded from collected output to prevent action metadata from trivially satisfying thresholds. - **Intermediate status check:** `plan status` check added between strategize and execute phases for stronger lifecycle validation, mirroring WF05 pattern. - **Spec divergences:** Documented via inline comments for each adaptation (resource_kind vs physical, includes vs include_skills, namespaced tool names, invariant count differences, omitted `--arg` parameters). ## Quality Gates | Gate | Status | |------|--------| | `nox -e lint` | ✅ Pass | | `nox -e typecheck` | ✅ Pass (0 errors) | | `nox -e unit_tests` | ✅ Pass (480 features, 12565 scenarios) | | `nox -e integration_tests` | ✅ Pass (1775/1775) | | `nox -e e2e_tests` | ✅ Pass (56/56, including WF08) | | `nox -e coverage_report` | ✅ Pass (98% ≥ 97%) |
test(e2e): workflow example 8 — cloud infrastructure management (supervised profile)
Some checks failed
CI / lint (pull_request) Successful in 28s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 19s
Details
CI / security (pull_request) Successful in 56s
Details
CI / typecheck (pull_request) Successful in 1m8s
Details
CI / e2e_tests (pull_request) Failing after 1m10s
Details
CI / integration_tests (pull_request) Successful in 3m45s
Details
CI / unit_tests (pull_request) Successful in 4m36s
Details
CI / docker (pull_request) Successful in 43s
Details
CI / coverage (pull_request) Successful in 7m1s
Details
CI / benchmark-regression (pull_request) Successful in 37m57s
Details
90585ba3a0 
E2E Robot Framework test for WF8: Cloud Infrastructure Management.

Scenario: Terraform infrastructure analysis using the supervised
automation profile.  Creates a temp repo with Terraform config files
(main.tf, variables.tf, outputs.tf), registers a custom
local/terraform-state resource type (copy_on_write sandbox), creates
an infrastructure-analysis action with invariants, registers a
git-checkout resource, creates a project with project-level
invariants, and drives the full plan lifecycle (plan use -> execute
strategize -> execute -> diff -> apply --yes).

Flexible assertions verify that infrastructure-related analysis
output is produced.  All LLM-dependent commands use expected_rc=None
for resilience.

ISSUES CLOSED: #754
freemo added this to the v3.1.0 milestone 2026-03-12 23:12:01 +00:00
freemo force-pushed test/e2e-wf08-cloud-infra from 90585ba3a0
Some checks failed
CI / lint (pull_request) Successful in 28s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 19s
Details
CI / security (pull_request) Successful in 56s
Details
CI / typecheck (pull_request) Successful in 1m8s
Details
CI / e2e_tests (pull_request) Failing after 1m10s
Details
CI / integration_tests (pull_request) Successful in 3m45s
Details
CI / unit_tests (pull_request) Successful in 4m36s
Details
CI / docker (pull_request) Successful in 43s
Details
CI / coverage (pull_request) Successful in 7m1s
Details
CI / benchmark-regression (pull_request) Successful in 37m57s
Details
to 72b34a0a88
Some checks failed
CI / lint (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 30s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 28s
Details
CI / build (pull_request) Successful in 21s
Details
CI / e2e_tests (pull_request) Successful in 45s
Details
CI / unit_tests (pull_request) Successful in 2m17s
Details
CI / integration_tests (pull_request) Successful in 2m41s
Details
CI / docker (pull_request) Successful in 51s
Details
CI / coverage (pull_request) Successful in 5m9s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 16:15:15 +00:00 Compare
freemo force-pushed test/e2e-wf08-cloud-infra from 72b34a0a88
Some checks failed
CI / lint (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 30s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 28s
Details
CI / build (pull_request) Successful in 21s
Details
CI / e2e_tests (pull_request) Successful in 45s
Details
CI / unit_tests (pull_request) Successful in 2m17s
Details
CI / integration_tests (pull_request) Successful in 2m41s
Details
CI / docker (pull_request) Successful in 51s
Details
CI / coverage (pull_request) Successful in 5m9s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 588f487abb
All checks were successful
CI / lint (pull_request) Successful in 17s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 23s
Details
CI / build (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / security (pull_request) Successful in 34s
Details
CI / e2e_tests (pull_request) Successful in 50s
Details
CI / unit_tests (pull_request) Successful in 3m6s
Details
CI / integration_tests (pull_request) Successful in 3m45s
Details
CI / docker (pull_request) Successful in 59s
Details
CI / coverage (pull_request) Successful in 6m1s
Details
CI / benchmark-regression (pull_request) Successful in 33m37s
Details
2026-03-13 16:24:05 +00:00 Compare
freemo force-pushed test/e2e-wf08-cloud-infra from 588f487abb
All checks were successful
CI / lint (pull_request) Successful in 17s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 23s
Details
CI / build (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / security (pull_request) Successful in 34s
Details
CI / e2e_tests (pull_request) Successful in 50s
Details
CI / unit_tests (pull_request) Successful in 3m6s
Details
CI / integration_tests (pull_request) Successful in 3m45s
Details
CI / docker (pull_request) Successful in 59s
Details
CI / coverage (pull_request) Successful in 6m1s
Details
CI / benchmark-regression (pull_request) Successful in 33m37s
Details
to 1dee645c6a
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / build (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / e2e_tests (pull_request) Failing after 29s
Details
CI / security (pull_request) Successful in 36s
Details
CI / unit_tests (pull_request) Successful in 2m4s
Details
CI / integration_tests (pull_request) Successful in 3m0s
Details
CI / docker (pull_request) Successful in 8s
Details
CI / coverage (pull_request) Successful in 5m31s
Details
CI / benchmark-regression (pull_request) Successful in 35m21s
Details
2026-03-13 23:19:39 +00:00 Compare
freemo commented 2026-03-14 04:44:30 +00:00
Author
Owner
Copy link

PM Review — Day 34

Status: Mergeable, 0 reviews, M2 (v3.1.0)
Author: @freemo

E2E test for WF08 (cloud infrastructure management, supervised profile). Retroactive M2 coverage.

Action Items

Who Action Deadline
@hurui200320 Peer review Day 37
## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M2 (v3.1.0) **Author**: @freemo E2E test for WF08 (cloud infrastructure management, supervised profile). Retroactive M2 coverage. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @hurui200320 | **Peer review** | Day 37 |
freemo modified the milestone from v3.1.0 to v3.6.0 2026-03-16 00:32:09 +00:00
freemo commented 2026-03-16 09:34:52 +00:00
Author
Owner
Copy link

PM Status — Day 36 (2026-03-16)

Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days.

Priority note: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order.

Assigned reviewer: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.

## PM Status — Day 36 (2026-03-16) Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days. **Priority note**: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order. **Assigned reviewer**: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.
freemo reviewed 2026-03-16 16:26:24 +00:00
freemo left a comment
Copy link

PM Day 36: M7 E2E test. Merge conflict. @freemo rebase needed. Lower priority than M3-M6 work.

PM Day 36: M7 E2E test. Merge conflict. @freemo rebase needed. Lower priority than M3-M6 work.
freemo commented 2026-03-16 22:23:04 +00:00
Author
Owner
Copy link

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on #628 and #966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on https://git.cleverthis.com/cleveragents/cleveragents-core/issues/628 and https://git.cleverthis.com/cleveragents/cleveragents-core/issues/966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.
freemo commented 2026-03-17 18:34:03 +00:00
Author
Owner
Copy link

PM Status — Day 37

Reviewers assigned. This PR needs at least 2 approving reviews per CONTRIBUTING.md before merge.

Author: Please ensure this PR is rebased on latest master and all quality gates pass before requesting merge.

PM status — Day 37

## PM Status — Day 37 Reviewers assigned. This PR needs at least 2 approving reviews per `CONTRIBUTING.md` before merge. **Author**: Please ensure this PR is rebased on latest `master` and all quality gates pass before requesting merge. --- *PM status — Day 37*
hurui200320 force-pushed test/e2e-wf08-cloud-infra from 1dee645c6a
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / build (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / e2e_tests (pull_request) Failing after 29s
Details
CI / security (pull_request) Successful in 36s
Details
CI / unit_tests (pull_request) Successful in 2m4s
Details
CI / integration_tests (pull_request) Successful in 3m0s
Details
CI / docker (pull_request) Successful in 8s
Details
CI / coverage (pull_request) Successful in 5m31s
Details
CI / benchmark-regression (pull_request) Successful in 35m21s
Details
to eb74e5aa30
Some checks failed
CI / lint (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 43s
Details
CI / security (pull_request) Successful in 51s
Details
CI / quality (pull_request) Successful in 27s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 15s
Details
CI / unit_tests (pull_request) Successful in 3m12s
Details
CI / integration_tests (pull_request) Successful in 3m37s
Details
CI / e2e_tests (pull_request) Failing after 4m31s
Details
CI / docker (pull_request) Successful in 10s
Details
CI / coverage (pull_request) Successful in 7m0s
Details
CI / benchmark-regression (pull_request) Successful in 38m53s
Details
2026-03-18 08:45:52 +00:00 Compare
hurui200320 force-pushed test/e2e-wf08-cloud-infra from eb74e5aa30
Some checks failed
CI / lint (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 43s
Details
CI / security (pull_request) Successful in 51s
Details
CI / quality (pull_request) Successful in 27s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 15s
Details
CI / unit_tests (pull_request) Successful in 3m12s
Details
CI / integration_tests (pull_request) Successful in 3m37s
Details
CI / e2e_tests (pull_request) Failing after 4m31s
Details
CI / docker (pull_request) Successful in 10s
Details
CI / coverage (pull_request) Successful in 7m0s
Details
CI / benchmark-regression (pull_request) Successful in 38m53s
Details
to 9a746d6195
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 22s
Details
CI / lint (pull_request) Successful in 3m21s
Details
CI / typecheck (pull_request) Successful in 4m7s
Details
CI / e2e_tests (pull_request) Failing after 11m49s
Details
CI / unit_tests (pull_request) Failing after 11m49s
Details
CI / integration_tests (pull_request) Failing after 16m49s
Details
CI / quality (pull_request) Failing after 16m49s
Details
CI / security (pull_request) Failing after 16m49s
Details
CI / coverage (pull_request) Successful in 11m42s
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 1s
Details
CI / benchmark-regression (pull_request) Successful in 53m55s
Details
2026-03-27 06:29:46 +00:00 Compare
hurui200320 force-pushed test/e2e-wf08-cloud-infra from 9a746d6195
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 22s
Details
CI / lint (pull_request) Successful in 3m21s
Details
CI / typecheck (pull_request) Successful in 4m7s
Details
CI / e2e_tests (pull_request) Failing after 11m49s
Details
CI / unit_tests (pull_request) Failing after 11m49s
Details
CI / integration_tests (pull_request) Failing after 16m49s
Details
CI / quality (pull_request) Failing after 16m49s
Details
CI / security (pull_request) Failing after 16m49s
Details
CI / coverage (pull_request) Successful in 11m42s
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 1s
Details
CI / benchmark-regression (pull_request) Successful in 53m55s
Details
to 8417a345c2
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 26s
Details
CI / lint (pull_request) Successful in 3m19s
Details
CI / quality (pull_request) Successful in 3m50s
Details
CI / typecheck (pull_request) Successful in 3m56s
Details
CI / security (pull_request) Successful in 4m13s
Details
CI / integration_tests (pull_request) Successful in 6m52s
Details
CI / unit_tests (pull_request) Successful in 7m32s
Details
CI / docker (pull_request) Successful in 1m11s
Details
CI / coverage (pull_request) Successful in 11m18s
Details
CI / status-check (pull_request) Successful in 3s
Details
CI / e2e_tests (pull_request) Failing after 25m57s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-27 09:45:38 +00:00 Compare
hurui200320 force-pushed test/e2e-wf08-cloud-infra from 8417a345c2
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 26s
Details
CI / lint (pull_request) Successful in 3m19s
Details
CI / quality (pull_request) Successful in 3m50s
Details
CI / typecheck (pull_request) Successful in 3m56s
Details
CI / security (pull_request) Successful in 4m13s
Details
CI / integration_tests (pull_request) Successful in 6m52s
Details
CI / unit_tests (pull_request) Successful in 7m32s
Details
CI / docker (pull_request) Successful in 1m11s
Details
CI / coverage (pull_request) Successful in 11m18s
Details
CI / status-check (pull_request) Successful in 3s
Details
CI / e2e_tests (pull_request) Failing after 25m57s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to fb4d343245
All checks were successful
CI / build (pull_request) Successful in 30s
Details
CI / lint (pull_request) Successful in 4m1s
Details
CI / quality (pull_request) Successful in 4m37s
Details
CI / typecheck (pull_request) Successful in 4m48s
Details
CI / security (pull_request) Successful in 4m49s
Details
CI / integration_tests (pull_request) Successful in 9m37s
Details
CI / unit_tests (pull_request) Successful in 10m7s
Details
CI / docker (pull_request) Successful in 1m24s
Details
CI / coverage (pull_request) Successful in 11m27s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / e2e_tests (pull_request) Successful in 16m22s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h10m15s
Details
2026-03-27 10:48:25 +00:00 Compare
freemo self-assigned this 2026-04-02 06:15:24 +00:00
freemo commented 2026-04-02 17:34:35 +00:00
Author
Owner
Copy link

🤖 Backlog Groomer (groomer-1): Closing as duplicate of #754.

Issue #754 (test(e2e): workflow example 8 — cloud infrastructure management) is the canonical version with full labels (MoSCoW/Must have, Priority/Critical, State/In Review, Type/Testing) and milestone v3.6.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #754. Issue #754 (`test(e2e): workflow example 8 — cloud infrastructure management`) is the canonical version with full labels (`MoSCoW/Must have`, `Priority/Critical`, `State/In Review`, `Type/Testing`) and milestone `v3.6.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:34:50 +00:00
All checks were successful
CI / build (pull_request) Successful in 30s
Required
Details
CI / lint (pull_request) Successful in 4m1s
Required
Details
CI / quality (pull_request) Successful in 4m37s
Required
Details
CI / typecheck (pull_request) Successful in 4m48s
Required
Details
CI / security (pull_request) Successful in 4m49s
Required
Details
CI / integration_tests (pull_request) Successful in 9m37s
Required
Details
CI / unit_tests (pull_request) Successful in 10m7s
Required
Details
CI / docker (pull_request) Successful in 1m24s
Required
Details
CI / coverage (pull_request) Successful in 11m27s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / e2e_tests (pull_request) Successful in 16m22s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h10m15s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
hamza.khyari
brent.edwards
CoreRasurae
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.6.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
freemo
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#627 Implement @tdd_expected_fail tag handling in Behave environment
cleveragents/cleveragents-core
#628 Implement @tdd_expected_fail tag handling in Robot Framework
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core!794
No description provided.