Skip to content

test: smoke-test the central PR-e2e pipeline (do not merge) - #381

Open
bnsoni wants to merge 2 commits into
mainfrom
test/pr-e2e-pipeline-smoke
Open

test: smoke-test the central PR-e2e pipeline (do not merge)#381
bnsoni wants to merge 2 commits into
mainfrom
test/pr-e2e-pipeline-smoke

Conversation

@bnsoni

@bnsoni bnsoni commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Throwaway PR to exercise the new central PR-e2e pipeline end to end. Do not merge — delete the branch when done.

How to run it

Add the run-tests label. That is the only trigger.

What should happen

  1. gate passes (label present, not a fork)
  2. unit-tests + build-app-image run — the mentor SPA image, --no-cache, from this PR's merge commit
  3. The e2e job dispatches iblai/iblai-deploy-ops and streams phase progress into this log:
    [hh:mm:ssZ] resolve: success | baseline drift check: in_progress
    [hh:mm:ssZ] … | sync env → 1.116.0: in_progress      ← only if stg1 has drifted
    [hh:mm:ssZ] … | swap mentor → PR image: success | e2e: in_progress
    
  4. A comment appears on this PR with the verdict and a public link to the Playwright report + traces
  5. stg1's mentor SPA is restored to its original image (this always runs, even on failure)

Why this spec

The change is a comment only in one spec file, so the changed-spec detector picks selective mode and runs just 33-ui-render-console-errors.spec.ts rather than the ~50 min mentor suite. That spec is a single test that passed clean on the last full run, so a red result means the pipeline, not the app.

Expect roughly 10–15 min — most of it the Playwright image build. Longer on the first run if stg1 has to be synced to the prod release first.

What to check

  • the phase log is readable here, without opening the private repo
  • the PR comment lands, with a working report link
  • PR E2E Tests reports a conclusion
  • stg1 mentor is back on its original image afterwards

🤖 Generated with Claude Code

Comment-only change to one spec, so the changed-spec detector picks selective
mode and runs just this file instead of the ~50 min mentor suite.
@bnsoni
bnsoni requested a review from mamigot as a code owner July 29, 2026 03:00
@mamigot

mamigot commented Jul 29, 2026

Copy link
Copy Markdown
Member

Claude encountered an error —— View job


I'll analyze this and get back to you.

@bnsoni bnsoni added the run-tests Trigger PR validation pipeline label Jul 29, 2026
@github-actions

github-actions Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

PR E2E - OK

Full report, traces and screenshots

result OK
suite mentor - mode selective - env stg1
tested against prod release 1.126.0 (env was synced to it first)
failed 0
new failures 0

@bnsoni bnsoni added run-tests Trigger PR validation pipeline and removed run-tests Trigger PR validation pipeline labels Jul 29, 2026
The e2e orchestration moved into iblai/pr-e2e-action@v1. A pull_request event runs
from the merge ref, so this PR was still replaying the old inline caller. This is
the one-time bootstrap cost documented in docs/pr-e2e.md - after it, action changes
arrive without any further branch movement.
@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/status

3 similar comments
@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/status

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/status

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/status

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Status — #381

  • this PR's central run: completed/successcentral run 30967769025
  • this PR's caller run: completed/success
  • running now: nothing
  • waiting in the queue: 0

Runs serialize per environment, so a wait means the box is busy — not that anything is broken.
A full mentor suite is ~40–50 min. /retest <spec> re-runs one file in minutes.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/help

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

PR e2e commands

command what it does
/retest re-run the full suite
/retest <spec> re-run only matching spec files — minutes instead of ~45
/status where this PR is in the queue, and what is running
/report link to the latest report for this PR
/cancel stop this PR's run and free the environment

<spec> matches as a substring, so /retest 34 and /retest 34-workflows both work.
Several are allowed: /retest 34-workflows 50-chat.

Requires write access to this repo; fork PRs are not eligible.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/help

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

PR e2e commands

command what it does
/retest re-run the full suite
/retest <spec> re-run only matching spec files — minutes instead of ~45
/status where this PR is in the queue, and what is running
/report link to the latest report for this PR
/cancel stop this PR's run and free the environment

<spec> matches as a substring, so /retest 34 and /retest 34-workflows both work.
Several are allowed: /retest 34-workflows 50-chat.

Requires write access to this repo; fork PRs are not eligible.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/report

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

A central run exists (30967769025) but no report is published yet — it is probably still running. Try /status.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/report

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

A central run exists (30967769025) but no report is published yet — it is probably still running. Try /status.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/report

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Latest report — #381

Full report, traces and screenshots

success — 0 failed, 0 new

From central run 30967769025.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/report

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Latest report — #381

Full report, traces and screenshots

success — 0 failed, 0 new

From central run 30967769025.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/retest 33

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

{"mode":"selective","specs":"e2e/journeys/33-ui-render-console-errors.spec.ts","head_sha":"237e4f990cfcd6c2ad77ea5e469ca90d21550be9","by":"bnsoni"}

@github-actions github-actions Bot removed the run-tests Trigger PR validation pipeline label Aug 5, 2026
@github-actions github-actions Bot added the run-tests Trigger PR validation pipeline label Aug 5, 2026
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Re-running 1 spec file(s) — requested by @bnsoni

e2e/journeys/33-ui-render-console-errors.spec.ts

A selective run is typically a few minutes instead of ~45. /status for progress.

⚠️ This proves only these files. Push a commit, or /retest with no argument, for the full suite before merging.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/retest 33

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

⚠️ Could not start the run

The run-tests label was recycled but no run appeared. Please remove the label and add it
back by hand — that always works.

A maintainer should check the handler's PAT: a label change made with GITHUB_TOKEN
raises no events, so the trigger silently does nothing.

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/retest 33

@bnsoni bnsoni added run-tests Trigger PR validation pipeline and removed run-tests Trigger PR validation pipeline labels Aug 5, 2026
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Re-running 1 spec file(s) — requested by @bnsoni

e2e/journeys/33-ui-render-console-errors.spec.ts

A selective run is typically a few minutes instead of ~45. /status for progress.

⚠️ This proves only these files. Push a commit, or /retest with no argument, for the full suite before merging.

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

PR E2E - OK

Full report, traces and screenshots

result OK
central run 30971517679
commit 237e4f99
suite mentor - mode selective - env stg1
tested against prod release 1.126.0 (env was synced to it first)
failed 0
new failures 0

@bnsoni

bnsoni commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/report

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Latest report — #381

Full report, traces and screenshots

success — 0 failed, 0 new

From central run 30971517679.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

run-tests Trigger PR validation pipeline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants