Canary failing: staging SaaS smoke #1997

Closed
opened 2026-05-28 20:36:12 +00:00 by gitea-actions · 163 comments

Smoke run failed at 2026-05-28T20:36:12Z.

Run: https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/148025

This issue auto-closes on the next green smoke run. Consecutive failures add a comment here rather than a new issue.

Smoke run failed at 2026-05-28T20:36:12Z. Run: https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/148025 This issue auto-closes on the next green smoke run. Consecutive failures add a comment here rather than a new issue.
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/148175
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/148330
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/148542
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/148698
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/148864
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/149032
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/149204
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/149429
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/149587
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/149746
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/149899
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/150107
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/150269
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/150432
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/150586
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/157300
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/157468
Owner

needs-hongming hourly CI/security triage evidence (2026-05-30 15:10 PDT / 22:10 UTC)

Fresh current-head evidence for molecule-core/main@5fce77aac9:

  • Latest per-context status counts from Gitea commit-status API: failure=1, pending=3, success=35.
  • Log-backed failure 1: Continuous synthetic E2E run 99508 job 0 reached tenant provisioning, then timed out waiting for TLS/DNS. Diagnostic showed no DNS resolution for e2e-20260530-synth-164223.staging.moleculesai.app; teardown was accepted and AWS leak check found no live EC2 for the slug.
  • Log-backed failure 2: full-lifecycle E2E run 99468 job 1 reached tenant URL and provisioned parent/child workspaces, then parent workspace 259a9f4b-c380-4673-b887-a70289794482 moved to failed at 19:15:14Z and did not recover before teardown. AWS leak check was clean.
  • Secret/security contexts sampled at this head are green where completed: Secret scan success, forbidden tenant-env lint success, ci-required-drift success.

Impact: staging SaaS/canary coverage is currently red for both tenant DNS readiness and workspace bootstrap/recovery paths, so this is not just a stale status row. Please decide whether this should be owned under the controlplane tenant-DNS/provisioning queue or the workspace bootstrap watcher queue; I did not rerun workflows, mutate branch protection, rotate secrets, merge, force-push, or push to main.

needs-hongming hourly CI/security triage evidence (2026-05-30 15:10 PDT / 22:10 UTC) Fresh current-head evidence for molecule-core/main@5fce77aac914faf67681f8f5d712d0ef2ad26258: - Latest per-context status counts from Gitea commit-status API: failure=1, pending=3, success=35. - Log-backed failure 1: Continuous synthetic E2E run 99508 job 0 reached tenant provisioning, then timed out waiting for TLS/DNS. Diagnostic showed no DNS resolution for e2e-20260530-synth-164223.staging.moleculesai.app; teardown was accepted and AWS leak check found no live EC2 for the slug. - Log-backed failure 2: full-lifecycle E2E run 99468 job 1 reached tenant URL and provisioned parent/child workspaces, then parent workspace 259a9f4b-c380-4673-b887-a70289794482 moved to failed at 19:15:14Z and did not recover before teardown. AWS leak check was clean. - Secret/security contexts sampled at this head are green where completed: Secret scan success, forbidden tenant-env lint success, ci-required-drift success. Impact: staging SaaS/canary coverage is currently red for both tenant DNS readiness and workspace bootstrap/recovery paths, so this is not just a stale status row. Please decide whether this should be owned under the controlplane tenant-DNS/provisioning queue or the workspace bootstrap watcher queue; I did not rerun workflows, mutate branch protection, rotate secrets, merge, force-push, or push to main.
Owner

needs-hongming hourly CI/security triage evidence (2026-05-30 16:10 PDT / 23:10 UTC)

Fresh current-head evidence for molecule-core/main@5fce77aac9:

  • Robust latest-per-context status calculation currently has no latest failure/error rows, but 4 latest pending contexts: Continuous synthetic E2E, full-lifecycle E2E, staging SaaS smoke, and ci-arm64-advisory.
  • Direct logs show the live/pending E2E surfaces are still unhealthy and are converging on the same workspace bootstrap failure class:
    • Continuous synthetic E2E run 99517/job0: tenant reached DNS/TLS and parent workspace 3d181108-788d-4e49-8019-8b6ebe8274d6 moved provisioning -> failed at 21:46:47Z, then waited for bootstrap-watcher recovery.
    • Staging SaaS smoke run 99479/job0: tenant reached DNS/TLS and parent workspace aa8bb479-568d-473a-9c27-1e39b6fd06ab moved provisioning -> failed at 19:16:09Z, then waited for bootstrap-watcher recovery.
    • Full-lifecycle rerun 99468/job1: tenant reached DNS/TLS and parent workspace c747f572-0528-4e9f-9940-b2e30b04d5d4 moved provisioning -> failed at 23:11:09Z, then waited for bootstrap-watcher recovery.
  • This updates the prior hour's evidence: the DNS timeout class was not reproduced in these newer runs; the current repeating failure is workspace bootstrap/recovery.
  • OBS/Loki query for workspace c747f572-0528-4e9f-9940-b2e30b04d5d4 was attempted but returned HTTP 403 from obs.moleculesai.app, so this comment uses retained Gitea logs as evidence.

Impact: staging canaries are not clean even when tenant DNS/TLS succeeds. Please route ownership to the bootstrap-watcher/workspace provisioning path (or confirm if this belongs under an existing cp#245 follow-up). I did not rerun workflows, mutate branch protection, rotate secrets, deploy, restart runners, merge, force-push, or push to main.

needs-hongming hourly CI/security triage evidence (2026-05-30 16:10 PDT / 23:10 UTC) Fresh current-head evidence for molecule-core/main@5fce77aac914faf67681f8f5d712d0ef2ad26258: - Robust latest-per-context status calculation currently has no latest failure/error rows, but 4 latest pending contexts: Continuous synthetic E2E, full-lifecycle E2E, staging SaaS smoke, and ci-arm64-advisory. - Direct logs show the live/pending E2E surfaces are still unhealthy and are converging on the same workspace bootstrap failure class: - Continuous synthetic E2E run 99517/job0: tenant reached DNS/TLS and parent workspace 3d181108-788d-4e49-8019-8b6ebe8274d6 moved provisioning -> failed at 21:46:47Z, then waited for bootstrap-watcher recovery. - Staging SaaS smoke run 99479/job0: tenant reached DNS/TLS and parent workspace aa8bb479-568d-473a-9c27-1e39b6fd06ab moved provisioning -> failed at 19:16:09Z, then waited for bootstrap-watcher recovery. - Full-lifecycle rerun 99468/job1: tenant reached DNS/TLS and parent workspace c747f572-0528-4e9f-9940-b2e30b04d5d4 moved provisioning -> failed at 23:11:09Z, then waited for bootstrap-watcher recovery. - This updates the prior hour's evidence: the DNS timeout class was not reproduced in these newer runs; the current repeating failure is workspace bootstrap/recovery. - OBS/Loki query for workspace c747f572-0528-4e9f-9940-b2e30b04d5d4 was attempted but returned HTTP 403 from obs.moleculesai.app, so this comment uses retained Gitea logs as evidence. Impact: staging canaries are not clean even when tenant DNS/TLS succeeds. Please route ownership to the bootstrap-watcher/workspace provisioning path (or confirm if this belongs under an existing cp#245 follow-up). I did not rerun workflows, mutate branch protection, rotate secrets, deploy, restart runners, merge, force-push, or push to main.
Member

17:10 PDT heartbeat re-check with fresh Gitea status/log evidence:

  • molecule-core/main@5fce77aac9 latest statuses: no failure/error, but 4 contexts still report pending.
  • Fresh full lifecycle run 99468/job/1 started at 2026-05-31T00:13Z and is actively running; log reached tenant provisioning (status -> provisioning) after CP/secret preflights passed.
  • Older continuous synthetic run 99517/job/0 got tenant running/TLS OK, created parent+child workspaces, then parent workspace moved provisioning -> failed at 21:46Z and entered heartbeat-recovery wait.
  • Older 30-minute smoke run 99479/job/0 got tenant running/TLS OK, created parent workspace, then parent workspace moved provisioning -> failed at 19:16Z and entered heartbeat-recovery wait.
  • ci-arm64-advisory run 99462/job/0 is still queued/not started (job is not started).

So the current head is not red, but the stale/pending SaaS contexts are still backed by real workspace bootstrap/recovery failures plus queue lag. No secret values were printed; evidence came from token-authenticated Gitea logs.

17:10 PDT heartbeat re-check with fresh Gitea status/log evidence: - `molecule-core/main@5fce77aac9` latest statuses: no `failure`/`error`, but 4 contexts still report `pending`. - Fresh full lifecycle run `99468/job/1` started at 2026-05-31T00:13Z and is actively running; log reached tenant provisioning (`status -> provisioning`) after CP/secret preflights passed. - Older continuous synthetic run `99517/job/0` got tenant running/TLS OK, created parent+child workspaces, then parent workspace moved `provisioning -> failed` at 21:46Z and entered heartbeat-recovery wait. - Older 30-minute smoke run `99479/job/0` got tenant running/TLS OK, created parent workspace, then parent workspace moved `provisioning -> failed` at 19:16Z and entered heartbeat-recovery wait. - `ci-arm64-advisory` run `99462/job/0` is still queued/not started (`job is not started`). So the current head is not red, but the stale/pending SaaS contexts are still backed by real workspace bootstrap/recovery failures plus queue lag. No secret values were printed; evidence came from token-authenticated Gitea logs.
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/165292
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/165458
Member

18:10 PDT heartbeat re-check with fresh status/log evidence:

  • molecule-core/main@5fce77aac9 latest-per-context is now red again: E2E Staging SaaS (full lifecycle) / E2E Staging SaaS (push) failed in run 99468/job/1 at 2026-05-31T00:18:15Z.
  • This is a different terminal point than the earlier bootstrap-watcher failures:
    • CP reachable, staging tenant provisioned and TLS/DNS worked.
    • Parent and child workspaces both reached online and were routable.
    • Image upload/download, canvas-terminal diagnose, files API config.yaml PUT, and post-PUT routing recovery all passed.
    • Failure occurred at step 8/11 Sending A2A message to parent: A2A returned an error-shaped response: Error: message contained no text content.
    • Teardown was accepted and AWS leak check reported no live EC2 instances for slug e2e-20260531-163572-4.
  • Remaining stale/pending context: ci-arm64-advisory / fast-checks (push) is still queued/not started from run 99462/job/0.

Security/secret posture around this run: latest secret-token scans remain green (Secret scan, Lint no tenant GITEA or GITHUB token write, and Sweep stale AWS Secrets Manager secrets all succeeded). No secret values were printed.

18:10 PDT heartbeat re-check with fresh status/log evidence: - `molecule-core/main@5fce77aac9` latest-per-context is now red again: `E2E Staging SaaS (full lifecycle) / E2E Staging SaaS (push)` failed in run `99468/job/1` at 2026-05-31T00:18:15Z. - This is a different terminal point than the earlier bootstrap-watcher failures: - CP reachable, staging tenant provisioned and TLS/DNS worked. - Parent and child workspaces both reached `online` and were routable. - Image upload/download, canvas-terminal diagnose, files API `config.yaml` PUT, and post-PUT routing recovery all passed. - Failure occurred at step `8/11 Sending A2A message to parent`: `A2A returned an error-shaped response: Error: message contained no text content.` - Teardown was accepted and AWS leak check reported no live EC2 instances for slug `e2e-20260531-163572-4`. - Remaining stale/pending context: `ci-arm64-advisory / fast-checks (push)` is still queued/not started from run `99462/job/0`. Security/secret posture around this run: latest secret-token scans remain green (`Secret scan`, `Lint no tenant GITEA or GITHUB token write`, and `Sweep stale AWS Secrets Manager secrets` all succeeded). No secret values were printed.
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/165615
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/165775
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/165946
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/166096
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/166251
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/166402
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/166558
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/166713
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/166871
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/167022
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/167831
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/168028
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/168333
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/168506
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/168674
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/168831
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/168986
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/169137
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/169292
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/169442
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/169599
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/169750
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/169905
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/170055
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/170210
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/170360
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/170515
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/170665
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/170820
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/170971
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/171127
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/171283
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/171441
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/171652
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/171807
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/171969
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/172132
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/172282
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/172437
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/172587
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/172800
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/172970
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/173143
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/173303
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/173466
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/173654
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/173812
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/173965
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/174160
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/177946
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/178098
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/178277
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/178532
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/178706
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/178876
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/179056
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/179286
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/179456
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/180770
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/181040
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/181241
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/181474
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/181637
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/181789
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/182009
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/182209
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/182439
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/182589
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/182796
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/182969
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/183130
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/183304
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/183463
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/194157
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/194382
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/194559
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/194774
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/194988
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/195151
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/195313
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/195486
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/195682
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/195856
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/196054
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/196343
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/196546
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/196785
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/196959
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/197160
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/197349
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/197568
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/197729
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/197926
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/198153
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/198373
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/198593
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/198817
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/199026
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/199259
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/199490
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/199709
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/200041
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/200197
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/200359
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/200547
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/200882
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/201055
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/201226
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/201461
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/201676
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/201887
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/202125
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/202334
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/202615
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/202895
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/203118
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/203340
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/203590
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/203798
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/204088
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/204520
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/204784
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/205054
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/205400
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/205585
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/205802
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/206160
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/206400
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/206655
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/207003
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/207416
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/207945
Member

MECHANISM: The current scheduled staging failures are now failing before the A2A empty-content path tracked in #2204. Both staging-smoke.yml and continuous-synth-e2e.yml pin the claude-code canary to E2E_MODEL_SLUG=MiniMax-M2 (.gitea/workflows/staging-smoke.yml:112-117, .gitea/workflows/continuous-synth-e2e.yml:130-136; full SaaS has the same fallback at .gitea/workflows/e2e-staging-saas.yml:175). tests/e2e/test_staging_full_saas.sh:412-418 sends that model in the parent /workspaces create payload; the tenant is reachable, secrets are present, then the POST returns HTTP 400 and exits because tenant_call uses curl -f.

EVIDENCE: smoke job 277091 on core main 376e6ab89abf reaches TENANT_URL=https://e2e-smoke-20260604-smoke-207945..., logs MODEL_SLUG=MiniMax-M2, then curl: (22) ... 400. synth job 277121 shows the same sequence for synth-207973. The secret checks passed (LLM key present, admin token evaluated as masked), so this is not a missing-token failure.

RECOMMENDED FIX SHAPE: In molecule-core, update the staging smoke/synth/full-SaaS workflow model defaults to a provider-registry-valid claude-code MiniMax slug, or have the harness resolve the model from the same runtime/provider registry used by workspace create. Also improve tenant_call error capture so future 400 responses include the JSON body instead of losing the server's validation reason behind curl -f.

MECHANISM: The current scheduled staging failures are now failing before the A2A empty-content path tracked in #2204. Both `staging-smoke.yml` and `continuous-synth-e2e.yml` pin the claude-code canary to `E2E_MODEL_SLUG=MiniMax-M2` (`.gitea/workflows/staging-smoke.yml:112-117`, `.gitea/workflows/continuous-synth-e2e.yml:130-136`; full SaaS has the same fallback at `.gitea/workflows/e2e-staging-saas.yml:175`). `tests/e2e/test_staging_full_saas.sh:412-418` sends that model in the parent `/workspaces` create payload; the tenant is reachable, secrets are present, then the POST returns HTTP 400 and exits because `tenant_call` uses `curl -f`. EVIDENCE: smoke job `277091` on core main `376e6ab89abf` reaches `TENANT_URL=https://e2e-smoke-20260604-smoke-207945...`, logs `MODEL_SLUG=MiniMax-M2`, then `curl: (22) ... 400`. synth job `277121` shows the same sequence for `synth-207973`. The secret checks passed (`LLM key present`, admin token evaluated as masked), so this is not a missing-token failure. RECOMMENDED FIX SHAPE: In `molecule-core`, update the staging smoke/synth/full-SaaS workflow model defaults to a provider-registry-valid claude-code MiniMax slug, or have the harness resolve the model from the same runtime/provider registry used by workspace create. Also improve `tenant_call` error capture so future 400 responses include the JSON body instead of losing the server's validation reason behind `curl -f`.
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/208130
Member

MECHANISM: Recurrence on runs 208130 and 208163 confirms the scheduled smoke/synth failure is still the same invalid canary model-default path. The workflows evaluate E2E_MODEL_SLUG=MiniMax-M2; tests/e2e/test_staging_full_saas.sh sends it in /workspaces, and staging returns HTTP 400 immediately after tenant/admin-token setup. This remains before the #2204 A2A empty-content stage.

EVIDENCE: smoke job 277299 and synth job 277336 both log tenant/admin-token success, MODEL_SLUG=MiniMax-M2, then curl: (22) ... 400. Secrets are present (LLM key present, admin token retrieved). Log excerpt: MODEL_SLUG=MiniMax-M2.

RECOMMENDED FIX SHAPE: Update the scheduled staging canary workflow defaults to a provider-registry-valid claude-code MiniMax slug or resolve from registry, and capture the 400 response body in tenant_call so future validation failures keep the server reason.

MECHANISM: Recurrence on runs `208130` and `208163` confirms the scheduled smoke/synth failure is still the same invalid canary model-default path. The workflows evaluate `E2E_MODEL_SLUG=MiniMax-M2`; `tests/e2e/test_staging_full_saas.sh` sends it in `/workspaces`, and staging returns HTTP 400 immediately after tenant/admin-token setup. This remains before the #2204 A2A empty-content stage. EVIDENCE: smoke job `277299` and synth job `277336` both log tenant/admin-token success, `MODEL_SLUG=MiniMax-M2`, then `curl: (22) ... 400`. Secrets are present (`LLM key present`, admin token retrieved). Log excerpt: `MODEL_SLUG=MiniMax-M2`. RECOMMENDED FIX SHAPE: Update the scheduled staging canary workflow defaults to a provider-registry-valid claude-code MiniMax slug or resolve from registry, and capture the 400 response body in `tenant_call` so future validation failures keep the server reason.
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/208393
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/208686
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/208956
Smoke still failing. https://git.moleculesai.app/molecule-ai/molecule-core/actions/runs/209200
Member

Fixed in PR !2240.

  • Updated canary default model slug from MiniMax-M2 to MiniMax-M2.7 in all workflow files and dispatch logic.
  • Updated regression tests and error messages to match the new default.
  • The next scheduled smoke/synth run should pick up the new slug and hopefully go green.
Fixed in PR !2240. - Updated canary default model slug from `MiniMax-M2` to `MiniMax-M2.7` in all workflow files and dispatch logic. - Updated regression tests and error messages to match the new default. - The next scheduled smoke/synth run should pick up the new slug and hopefully go green.
Sign in to join this conversation.
5 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1997