Skip to content

ci: run single-node smoke only and disable multinode - #6907

Closed
warku123 wants to merge 3 commits into
tronprotocol:developfrom
warku123:ci/integration-smoke-disable-multinode
Closed

ci: run single-node smoke only and disable multinode#6907
warku123 wants to merge 3 commits into
tronprotocol:developfrom
warku123:ci/integration-smoke-disable-multinode

Conversation

@warku123

@warku123 warku123 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

  • Switches the single-node integration CI to run only the smoke test subset (--clean --smoke instead of the full suite)
  • Disables the multinode integration CI (--all) triggers, keeping workflow_dispatch for manual runs
  • Renames the single-node workflow, job, steps, and report artifact from "Full" to "Smoke" to reflect the actual scope

Why are these changes required?

Per the QA/integration-test team:

  • The smoke suite is the concise core integration test path; QA guarantees it stays valid and effective in CI. If we need additional coverage, we can request QA to add cases to the smoke suite.
  • The multinode suite (--all) is QA's own regression suite — complex, not recommended for our CI, and not maintained by QA for CI usage. Its execution time will only grow over time, making it increasingly unsuitable as a PR gate.
  • The full single-node suite is likewise unstable in CI today (its hardened assertions don't match the fixture baked into the troninfra/troninfra-ci image, causing stable failures unrelated to PR code).

Gating PRs on the smoke subset restores a reliable, QA-backed CI signal.

This PR has been tested by:

  • Unit Tests
  • Manual Testing (workflow YAML validated; smoke run verified green on fork PR — smokeTest task, 74 passed / 0 failed)

Follow up

  • Coordinate with QA if more integration coverage is needed — new cases should be added to the smoke suite
  • Multinode (--all) remains available via manual workflow_dispatch

Extra details

No production code changes; CI configuration only.

…de CI

Both integration suites are currently unstable per the integration-test
team, so gate PRs on the smoke subset only:

- single-node: pass --smoke to run only the smoke test subset
- multinode: comment out push/pull_request triggers, keep
  workflow_dispatch for manual runs
The shell comment lines between the image name and --clean --smoke
caused the args to be dropped, so the container ran the default full
:test suite (1691 tests) instead of smokeTest. Move the rationale
into the step name/comments above the command so the args are passed
cleanly.
@warku123 warku123 changed the title ci(integration): run single-node suite as smoke only, disable multinode CI ci(integration): run single-node smoke only, disable multinode Aug 5, 2026
@warku123 warku123 changed the title ci(integration): run single-node smoke only, disable multinode test: run single-node smoke only and disable multinode CI Aug 5, 2026
@warku123 warku123 changed the title test: run single-node smoke only and disable multinode CI ci: run single-node smoke only and disable multinode Aug 5, 2026
@warku123 warku123 closed this Aug 5, 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.

1 participant