Skip to content

[Bug]: QA Smoke scripts can invalidate dist used by flow Gateways #99734

Description

@RomneyDa

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

QA Smoke can delete or partially rewrite the shared dist/ tree while flow scenarios are running, causing Gateway startup or module loading failures.

Steps to reproduce

  1. Run QA Smoke on OpenClaw PR improve(qa): execute runtime scenarios through Docker #99705 head 37783c3502e427b47a24370af24fb4c50ef0c625.
  2. Include script-backed Docker scenarios and flow scenarios in the same unified QA selection.
  3. Observe script scenario package preparation rebuilding shared package artifacts while flow partitions launch Gateways from the same checkout.
  4. Observe Gateway failures for missing dist/index.js or generated dist/*.js chunks.

Expected behavior

Unified QA scheduling must prevent script scenario builds from mutating shared package artifacts while flow Gateways are starting or running.

Actual behavior

QA Smoke run 28688380283 failed on both attempts. Attempt 1 job 85085115629 could not find dist/index.js; attempt 2 job 85085991786 reported missing generated chunks including dist/errors-1gsKj1Z_.js while Gateway processes were running. The exact-head targeted Docker run 28688381529 passed all five selected Docker lane groups, isolating the failure to shared QA orchestration rather than the underlying scenarios. Current-main run 28688016374 passed without the newly script-backed Docker scenarios.

OpenClaw version

PR #99705 head 37783c3502e427b47a24370af24fb4c50ef0c625

Operating system

GitHub Actions Linux runner

Install method

Repository checkout with pnpm CI workflow

Model

QA mock provider configuration

Provider / routing chain

QA Lab flow scenarios -> local mock provider

Additional provider/model setup details

NOT_ENOUGH_INFO

Logs, screenshots, or supporting evidence

Impact and frequency

Blocks QA Smoke validation when unified QA selections combine flow scenarios with script scenarios that rebuild shared package artifacts. The exact-head run failed twice with two different missing-dist symptoms.

Additional context

The intended fix is orchestration isolation only. The Docker scenario implementation in #99705 remains separate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.maintainerMaintainer-authored PRmaturity:stableIssue affects a taxonomy feature currently scored M4/M5.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions