Skip to content

ci(conflict): Run the Tango MySQL suite in CI and load its schema locally - #918

Open
manjari25 wants to merge 1 commit into
manjari/tango-fake-serverfrom
manjari/tango-schema-ci
Open

manjari25 wants to merge 1 commit into
manjari/tango-fake-serverfrom
manjari/tango-schema-ci

Conversation

@manjari25

Copy link
Copy Markdown
Contributor

Why?

The tango analyzer keeps batch signatures in two MySQL tables, target_signature and target_dictionary. Their integration suite never ran in CI, and the local database setup did not create the tables, so a stack that uses the analyzer would fail on its first signature write.

What?

  • Adds a conflict-integration-test job to CI, which runs //test/integration/submitqueue/extension/conflict/..., and adds it to the required-checks gate.
  • make local-init-submitqueue-schemas now also applies the Tango schema to the application database.
  • TESTING.md lists the Tango schema directory under the application database.

Test Plan

  • make local-init-submitqueue-schemas against a running local stack applies the Tango schema.
  • The new CI job runs the conflict integration suite.

Issue

@manjari25
manjari25 added this pull request to stack #912 October 22, 2026 06:05
@manjari25
manjari25 marked this pull request as ready for review October 22, 2026 06:10
@manjari25
manjari25 requested review from a team, behinddwalls and sbalabanov as code owners October 22, 2026 06:10
@manjari25
manjari25 force-pushed the manjari/tango-schema-ci branch from a87d367 to 3360c0f Compare October 22, 2026 19:03

This branch has not been deployed

No deployments
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