Skip to content

test: stop five e2e and integration tests failing on host timing - #17259

Merged
chenmingwei23 merged 1 commit into
mainfrom
refactor/df-f06-e2e-integration-reds
Oct 6, 2026
Merged

chenmingwei23 merged 1 commit into
mainfrom
refactor/df-f06-e2e-integration-reds

Conversation

@bolichen97

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Five browser, end-to-end and in-process-gateway tests stop failing for reasons that have nothing to do with the change under test: a slow third-party font server, a Windows file-sharing window, a loaded runner's clock, or another test's data.

Each of these was seen red in CI or reds under a forced condition on the parent commit, with nothing wrong in the diff it was judging:

  • i18n render gate (E2E offline job, main run 37034645869): /developer?tab=config never went quiet in 10000ms ... Still in flight: https://fonts.googleapis.com/css2?....
  • Integration boot smoke (2 runs, job 111366821825 and 111360126393): test_a_second_boot_touches_only_known_module_globals named security.paths._path_resolve_thread_waits.
  • E2E Gateway Boot (windows-latest) (job 111414333087): PermissionError: [Errno 13] opening the live gateway's config.json.
  • Two-chat streaming fairness (test_streaming.py): its ordering held only while the second turn started within ~14.5 s of wall time.
  • hooks.spec.ts: ten fixed sleeps, three tests that silently skip their own body, a test that deletes whatever hook sorts first, and an afterAll cleanup that never matches anything.

Why it matters

A red that is not the PR's fault costs a rerun, hides real failures among the noise, and teaches people to rerun until green. The boot-smoke and i18n reds landed on unrelated PRs and on main; the hooks spec could delete a developer's own first hook when pointed at a live gateway.

Not a goal

  • No production behaviour change: only test code, the test harness, the i18n gate script and the test-only fake ACP backend change.
  • Not the Playwright config, its retries or worker count, nor any other Playwright spec.
  • Not the testing conventions or E2E docs beyond the one testing-conventions.md paragraph that described the replaced streaming pattern.
  • Not the shared quiet tracker in website/scripts/lib/render-settle.mjs.

What changed (motivation → approach → change)

Test Root cause Change
i18n render gate index.html requests the Google Fonts stylesheet on every navigation; routing turns the HTTP cache off, so each of ~124 captures waits on a live third-party answer, and one stall exceeds the 10 s quiet window. A truly offline host fails fast and passes. A context route answers the fonts stylesheet with empty CSS and refuses every other off-origin request, so both sweeps measure the same fallback face. Loopback requests are untouched and still counted.
Boot smoke witness The second-boot diff also reads state that moves with wall time: resolver wait accounting, TTL caches, a periodic thread sampler, host probes on their own backoff. The test harness (test/integration/conftest.py) resets home- or run-derived state per boot in _reset_home_bound_globals (resolver bookkeeping, status-count cache, inventory gauges, thread-ledger baseline). Host clocks are listed with their reason. A new test seeds a cooldown and a cached count and proves both reset points drop them.
Boot matrix The test opened config.json while the gateway rewrites it by temp file plus os.replace; Windows refuses that open. Read agent.sandbox / agent.provider from GET /api/config/kirocrew; the test never opens the live file.
Streaming fairness Ordering raced a fixed 15 s stream. New opt-in [[SLOW_HOLD:<token>]] marker in src/kiro_crew/testing/fake_acp_backend.py: one chunk, then a hold until the test creates the token's release file. The test proves B streams while A is held and A streams while B is held. [[SLOW]] is unchanged.
hooks.spec.ts Shared store, fixed sleeps, isVisible branches, page-wide .first(). Each test seeds its own uniquely named hook over the API, waits on page and response signals, asserts the outcome in the UI and the API, and a fixture deletes only the ids it created. The ten titles are unchanged.

docs/system-specs/common/testing-conventions.md's paragraph on ordering two chat turns now points at the hold marker instead of [[SLOW]]'s cadence.

Harness isolation found on the way: the in-process integration gateway reads the developer's home wherever production does, so on a developer machine the onboarding import scan walked their foreign agents' homes and a credit refresh read kiro-cli's credential stores. isolate_user_home (called by integration_home) isolates the integration harness from the developer's local credential stores and home-derived paths: HOME, USERPROFILE, APPDATA/LOCALAPPDATA and the XDG data, cache and state roots point at an empty tmp sibling of KIROCREW_HOME, PATH leads with the test interpreter's directory (a home and its PATH move together), every declared home-override variable is dropped, and the credit pill's credential reader is stubbed. Its store paths stay where import bound them, as the repository's security-anchor rule requires. isolate_credentials drops the channel credentials, every AWS credential pointer acp.client.CREDENTIAL_POINTER_ENV_VARS declares plus the profile selectors, inline keys and AWS_ROLE_ARN, and the GH_/GITHUB_ names github_runner.GH_ENV_PASSTHROUGH forwards to gh; the aws CLI's two files point at paths that do not exist. The fake backend answers whoami with any flags (the credit refresh passes --format json) instead of falling into its ACP loop. No product code changes.

Backwards compatibility

Compatible: the fake backend's change is an added, opt-in marker; every existing marker and constant keeps its bytes. No production module changes.

Removes nothing: only test assertions, harness resets and one test-script route change; no product path, record or key is removed.

Tests

Every touched test went through the de-flake protocol on Linux, on a shared 32-CPU host, with /proc/loadavg recorded per run. "Parent" means the frozen base af1eb612d (the rebased base is 3c1e383dd; the only owned-file changes upstream are #17118 removing two crew-log witness entries and #17054's conventions additions, both carried). Out-of-tree probes forced each condition; none is committed. Every run started under env -i with a scratch HOME, KIROCREW_HOME and KIROCREW_WORKSPACE.

Test Forced condition: parent Same condition: this PR Repeats on this PR Negative control / mutation
i18n render gate (check-i18n-render.mjs) font host black-holed or held: exit 2, never went quiet ... Still in flight: https://fonts.googleapis.com/css2?... (the CI line); DNS failure (truly offline) passes exit 0 under both 20/20 sequential, 10/10 four-way parallel, full 62-surface sweep green, I18N_BASE_REF=6f70008e3 → PASS [vs-base] route disabled → exit 2 again
test_a_second_boot_touches_only_known_module_globals slow_thread 5/5 red (status_counts._counts_cache_ts, metrics.provider._consent_checked_at); one forced 0.15 s resolution in boot 2: red with the CI's exact _path_resolve_thread_waits slow_thread 8/8 green; forced resolution green file 36/36 at -n0; 10/10 at -n 4 with governance and update-shutdown co-tenants; whole integration layer in CI shape (-n 2) 51/51 on 5 runs, then 52/52 on 5 runs with the new isolation test drop _path_resolve_thread_waits.clear() → red by name; drop the cooldown or count reset → the new pin test reds
test_streaming.py second turn started 20 s late: B did not stream until A had finished green at 20 s and 30 s delays 48/48 at -n0 (slowest signal 0.12 s), 10/10 at -n 4 gateway serialises turns → B: a first chunk while A was held mid-turn ... did not arrive; hold never reached → red; hold dir unset → red
test_gateway_boot_matrix.py every first open of the live config.json refused the way Windows does: 3 failed with PermissionError: [Errno 13] at the CI frames 7/7 with every open refused, zero opens attempted 22/22 at -n0 (module convention; real gateways) swap the two tiers or the provider → each fails naming the resolved value
test_a_boot_reads_nothing_from_the_outer_home (new) boot under a stand-in outer home (credential stores, agent homes, every home variable): the parent and this branch's first commit both fail integration_home left kiro-cli's real credential reader live; with the reader asserted last, the parent reads its ~/.aws/sso/cache token files, CODEX_HOME and OPENCLAW_CONFIG_PATH, the first commit LOCALAPPDATA/hermes and OPENCLAW_CONFIG_PATH no read beneath the stand-in home, no scan root in it, no AWS or GitHub credential reaching the boot, reader replaced 20/20 at -n0, 5/5 after the last edit; slow_thread 1/1 drop the reader stub → reader live; wrap the real reader instead of stubbing it, with a store in the process's own home → the refresh opened kiro-cli's own credential stores; drop APPDATA/LOCALAPPDATA → scan resolves AppData/Local/hermes; drop the undeclared overrides → OPENCLAW_CONFIG_PATH/OPENCLAW_WORKSPACE_DIR; drop the import sources' variables → GEMINI_HOME, HERMES_HOME, OPENCLAW_STATE_DIR; drop the GitHub names → GH_TOKEN, GITHUB_TOKEN, ...; drop the AWS credential pointers → AWS_CONTAINER_*, ...
hooks.spec.ts one run: the fixture hook is deleted and an enabled Playwright_Test_Hook leaks; --workers=4 --fully-parallel --repeat-each=10: 1 failed; the old toggle "switch" resolved to the gateway-status button store unchanged after every run --workers=1 --repeat-each=10 100/100 (four times); --workers=4 --fully-parallel --repeat-each=10 with two co-tenant specs 210/210 (four times); all --retries=0 toggle no-op, delete no-op, blank test output, empty table, Save that creates nothing: the old spec passes all five, the new one fails each

The parent and first-commit reproductions run the new test module in those trees with one line back-ported: the _UNDECLARED_HOME_OVERRIDES constant the test reads, which is inert there; nothing else in those trees changes.

Decoy check: decoy credential stores, ~/.aws files, a GitHub login and agent homes were planted in the scratch HOME the pytest process starts with, and an out-of-tree audit probe recorded every read of them. This branch's first commit opens both decoy credential stores during the route sweep; this PR opens none over five runs of the new test and the whole integration layer in CI shape (52 passed).

The fake backend's hold has unit tests for release, cancel during the hold, expiry, a missing hold directory, a quoted marker and token validation (test_fake_acp_backend.py; module coverage 83% → 93%).

HOME pin: a probe recording every home the onboarding import scan resolves during the route sweep reads the operator's home on the parent and the empty tmp home with this PR (scan 16 s → 9 s for the test).

gil_hog (the card's named condition) also reds the parent (the witness names the same globals), but on this host it often pushes a boot past the harness's 60 s boot deadline in both parent and fix, so slow_thread is the reproducible proof. Unit owners of the fake and the shared helpers pass unmodified: test_fake_acp_backend.py, test_workflow_memory_backend_reset.py, test_e2e_recovery_wait.py (47 passed), plus 814 passed / 99 skipped across the targeted backend set, and 489 passed on the fake, identity-store, usage-API and host-isolation owners after the isolation fold (twice).

local-gate.py --dry-run selects 1005 backend and 323 frontend test files; per the campaign's capacity rule the backend set ran narrowly as above and CI owns the broad set. Exact-SHA Linux, Windows and macOS lanes: in the PR checks.

Follow-up outside this PR: website/src/i18n/render-baseline.json reads developer-mcp-pool.layout 0 -> 2 under the now-deterministic fallback face in the record-only path (no I18N_BASE_REF); CI decides with [vs-base], which compares like for like. A --build --update refresh belongs to the integration owner.

Manual verification

N/A — every change is to a test or a test harness, and each is exercised by the forced-condition and repeat runs above.

Related Issues

Part of #16536

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@bolichen97
bolichen97 requested a review from a team as a code owner October 6, 2026 06:34
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 6, 2026
@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of 3cd44ae01be8547abfea05bb3fc4cefd31257b97 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: PASS

Nothing to check.

[UX-REVIEWED] 3cd44ae

Description read

[DESCRIPTION-READ] 1de7dda47d5735eba0ac140ec48e49c18c5755ea27bdfdd849530d6154669106

That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 3cd44ae01be8547abfea05bb3fc4cefd31257b97 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

One thing to check: the i18n render gate now always measures layout in the fallback font, so text that overflows only in the real Google webfont is no longer caught.

[DESIGN-REVIEWED] 3cd44ae

Description read

[DESCRIPTION-READ] 78ac5d6b11b778ebfc02b38724f6615fa9f87390d8d32758776a7ce9738d3345

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — 🟡 CONCERNS

Premise-level review of 3cd44ae01be8547abfea05bb3fc4cefd31257b97 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: CONCERNS

The developer-home and credential isolation (isolate_user_home, a wider isolate_credentials, a 230-line audit-hook test, whoami flags) is new scope riding on a five-flake fix.

Not justified as shipped

  • Item 6 — rides along, oversized: the Goal is "Five browser, end-to-end and in-process-gateway tests stop failing", and the description calls this "Harness isolation found on the way". No flake or linked issue points at it, and none of the five fixes depends on it. It adds two new public harness helpers, two hand-kept env lists (_UNDECLARED_HOME_OVERRIDES, _AWS_IDENTITY_ENV), a process-wide sys.addaudithook, and drops the GH_/GITHUB_ and AWS pointer variables.
    Subtraction: move isolate_user_home, the isolate_credentials widening, test_a_boot_reads_nothing_from_the_outer_home with its outer_home fixture, and the whoami args[:1] change into their own PR. Keep the existing inline CREDENTIAL_KEYS/AWS deletion in integration_home.
    Clears when: the mechanism is removed, or a human amends the Goal.

What this change ships

Inventory (7 items) — 5 justified

Intent: stop five tests going red for host-timing or third-party reasons unrelated to the PR under test — FIX.

  1. The i18n render gate answers the Google Fonts stylesheet empty and refuses other off-origin requests — justified
  2. Boot smoke resets resolver, status-count, inventory and thread-sample state per boot, and lists host clocks as known changes — justified
  3. A new test seeds a cooldown and a cached count and proves both resets drop them — justified
  4. The boot matrix reads agent.sandbox/provider over the API instead of opening config.json — justified
  5. The fake backend gets an opt-in [[SLOW_HOLD:<token>]] marker, and the streaming test is rebuilt on it — justified
  6. Integration boots get an isolated HOME/XDG/PATH, more credential variables dropped, a stubbed credit reader and an outer-home read audit — rides along, oversized
  7. hooks.spec.ts seeds its own hooks, uses signal waits, and cleans up only the ids it created — justified

[FIRST-PRINCIPLES-REVIEWED] 3cd44ae

Description read

[DESCRIPTION-READ] a65428ffb82a35ef541feb524170ae39b71195595ca8aeb9fc0149d7f870b881

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 3cd44ae01be8547abfea05bb3fc4cefd31257b97 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 3cd44ae

Verdict parsed from the review's SHA-scoped output markers for commit 3cd44ae01be8547abfea05bb3fc4cefd31257b97.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 3cd44ae01be8547abfea05bb3fc4cefd31257b97: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 3cd44ae01be8547abfea05bb3fc4cefd31257b97 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 3cd44ae

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 3cd44ae01be8547abfea05bb3fc4cefd31257b97: <one-sentence reason>

@bolichen97

bolichen97 commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: integration_home keeps the developer's home and credentials out of the in-process boot

  • span=9f59ae95ce43 Item 8: harness home and credential isolation (rebutted)

Same class as the Goal: an in-process boot that reads the developer's real home depends on host state, not on the change under test. Before the HOME pin, the route sweep's onboarding import scan walked the real ~/.claude tree and could exceed the sweep's 10 s per-request bound on a developer host (scan 16 s with the real home, 9 s with the pin).
The HOME pin is code this PR adds, so finishing it is in scope. Moving HOME alone left the credit reader's store paths (bound from the real home at import), the home-override variables and the AWS/GitHub variables pointing at the developer's machine. isolate_user_home and isolate_credentials cover exactly those. The reader is stubbed rather than its paths moved because AUTOSDE no-test-side-effects forbids moving that anchor.
The audit-hook test pins that harness contract. It fails on this branch's first commit and on the parent, and dropping any one variable family fails it by name. The hook is installed once per worker and stays inert unless armed, the same pattern as test_portability.py.
Removing this would put the unbounded home walk and the credential-store reads back into every local integration run. CI runners behave the same either way.
Required by the reviewer's ruling; a partial home pin would still read operator credentials.

@bolichen97

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: the fake backend answers whoami with trailing flags

  • span=9a6a4010a844 Item 9: fake whoami accepts trailing flags (rebutted)

The credit refresh runs kiro-cli whoami --format json. The fake answered only a bare whoami, so that call fell into its ACP loop and ended only when stdin closed: about 1 s under pytest's captured stdin, a 30 s wait per call under -s.
Every integration test that drives /api/sessions/usage/refresh depended on that stdin, not only the new isolation test. The fake now answers the subcommand with any flags, the way it already answers chat --list-models. That is one condition in a test-only module.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • Design watch: the developer-home and credential isolation stays in this PR (answered)

It finishes the HOME pin this PR adds to integration_home. That pin is what stops the route sweep's onboarding scan walking the developer's real home past its 10 s per-request bound. Splitting it out would ship a half-moved home: credential-store paths bound at import, override variables and AWS/GitHub variables still pointing at the developer's machine.
It touches only test harness code this PR already owns (test/integration/conftest.py, test_boot_smoke.py), changes no product code, and the First Principles disposition on this head gives the evidence (the fail on the parent and the first commit, plus per-family mutations).

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 6, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Merged-tree probe (no push): current main at f08cefb528ca40b42f225b9b1ac54f49b48cada4 merged with this PR's head af4b2301bfedee18962a42d3cc57f91a03208d69 (git merge-tree --write-tree, clean; tree e454462d25c4d41cc1853cade1e498c08d650234). This checks the integration tests main added since this head went green (#16681, test/integration/test_script_cron_sessions.py), which use the integration_home / gateway_boot fixtures this PR changes.

KIROCREW_INTEGRATION=1 python -m pytest -n0 -p no:cacheprovider -q --no-cov --timeout=300 \
  test/integration/test_script_cron_sessions.py test/integration/test_boot_smoke.py
40 passed in 113 s   (25 in test_script_cron_sessions.py, 15 in test_boot_smoke.py)

Run from the merged tree's own src on Linux (Python 3.12). The process started with a clean environment (env -i) and a scratch HOME, KIROCREW_HOME, KIROCREW_WORKSPACE and TMPDIR. Host load at start was 21.7. No rebase was needed: the merge is clean, and green-age's overlap is with files in the same directory, not the same files.

@bolichen97
bolichen97 enabled auto-merge (squash) October 6, 2026 07:40
@bolichen97
bolichen97 force-pushed the refactor/df-f06-e2e-integration-reds branch from af4b230 to d680901 Compare October 6, 2026 09:19

Copy link
Copy Markdown
Contributor Author

Automated rebase onto main (5edf2feecba29b11ee42b39883ea3a04928ea319): head af4b2301bf → d680901734. Clean rebase, no conflicts; git range-diff shows the patch is identical (=). Checks: py_compile passes on changed Python files; test/test_fake_acp_backend.py 49 passed; test/integration/test_boot_smoke.py + test_streaming.py skipped locally (they need an opt-in environment). Pushed with --force-with-lease.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision readiness: checking Automated validation is still running labels Oct 6, 2026
Five browser, end-to-end and in-process-gateway tests went red on
runs whose diff had nothing to do with them. Each now waits on, or
removes, the thing it raced:

- i18n render gate: a context route answers the Google Fonts
  stylesheet with empty CSS and refuses every other off-origin
  request, so a slow third-party answer can no longer hold a capture
  past the quiet window, and both sweeps measure the same face.
- integration boot smoke: the per-boot reset list also clears the
  path-resolver bookkeeping, the status-count cache, the inventory
  gauges and the thread-ledger baseline, and host clocks on their own
  backoff are listed with their reason; a new test proves a seeded
  cooldown and cached count do not cross a boot.
- integration harness isolation: integration_home keeps the
  in-process gateway away from the developer's local credential
  stores and home-derived paths. HOME, USERPROFILE, APPDATA,
  LOCALAPPDATA and the XDG data, cache and state roots point at an
  empty tmp sibling, PATH leads with the test interpreter's directory,
  every declared home-override variable and every AWS and GitHub
  credential the environment carries is dropped, and the credit
  pill's credential reader is stubbed. A new test boots under a
  stand-in home and fails on any read beneath it, on a credential
  that reaches the boot, or if the real credential reader runs.
- E2E boot matrix: agent.sandbox and agent.provider are read from
  GET /api/config/kirocrew instead of opening the live gateway's
  config.json, which Windows refuses while the gateway replaces it.
- two-chat streaming: the fake ACP backend gains an opt-in
  [[SLOW_HOLD:<token>]] marker that holds a turn after one chunk until
  the test creates a release file, so "B streams while A is mid-turn"
  and "A streams while B is mid-turn" are constructed, not raced;
  unit tests pin its release, cancel and expiry paths. The fake also
  answers whoami with any flags, as the credit refresh calls it.
- hooks.spec.ts: every test seeds its own uniquely named hook through
  the API, waits on page and response signals, asserts the outcome in
  the UI and the API, and deletes only the ids it created.

The testing-conventions paragraph on ordering two chat turns now
points at the hold marker instead of [[SLOW]]'s cadence.
@bolichen97
bolichen97 force-pushed the refactor/df-f06-e2e-integration-reds branch from d680901 to 3cd44ae Compare October 6, 2026 10:18
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 6, 2026
@chenmingwei23
chenmingwei23 merged commit 499ba27 into main Oct 6, 2026
101 checks passed
@chenmingwei23
chenmingwei23 deleted the refactor/df-f06-e2e-integration-reds branch October 6, 2026 14:41
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants