Skip to content

Conversation

@amkCha
Copy link
Collaborator

@amkCha amkCha commented Nov 5, 2025

Note

Make releases publish only after unit and fast replay tests by default, add a reusable fast replay workflow, and refactor CI to consume it.

  • CI Workflows:
    • Reusable fast replay tests: Add ./.github/workflows/reusable-fast-replay-tests.yml to run :arithmetization:fastReplayTests and upload reports/artifacts.
    • Gradle tests (.github/workflows/gradle-tests.yml):
      • Replace inline replay-tests job with call to reusable-fast-replay-tests.yml.
      • Pass through tests-with-ssh to unit and replay tests.
    • Manual release (.github/workflows/manual-release.yml):
      • Add inputs wait-for-tests-bef-publish and tests-with-ssh.
      • Run unit tests (CANCUN, PRAGUE) and fast replay via reusable workflow.
      • Split publishing into:
        • publish-default: waits for tests (default) before ./gradlew publish with Cloudsmith creds.
        • publish-as-soon-as-ready: publishes immediately when wait-for-tests-bef-publish is false.
      • Remove duplicated inline replay test steps and migrate to reusable workflow.

Written by Cursor Bugbot for commit 03b6fea. This will update automatically on new commits. Configure here.

@amkCha amkCha marked this pull request as ready for review November 5, 2025 20:48
@amkCha amkCha force-pushed the feat/unit-replays-condition-to-jar-release branch from 9107e69 to eb7d3d9 Compare November 5, 2025 20:49
@amkCha amkCha force-pushed the feat/unit-replays-condition-to-jar-release branch from eb7d3d9 to 44987a2 Compare November 5, 2025 21:08
@amkCha amkCha force-pushed the feat/unit-replays-condition-to-jar-release branch from ba3d69d to 21e472d Compare November 10, 2025 18:22
Copy link
Collaborator

@DavePearce DavePearce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, looks fine. There is a comment from Cursor which I think should be addressed. The manual release either needs a tests-with-ssh or perhaps more easily just set it to false where its used.

# ==================================================================
# Publish release post tests
# ==================================================================
publish-conditional-to-units-and-replay-tests:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about the name here. This should be the default path, right? So I would just call it publish or perhaps publish-default.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's changed :)

@amkCha amkCha force-pushed the feat/unit-replays-condition-to-jar-release branch from 21e472d to 9b7a84b Compare November 13, 2025 21:49
@amkCha amkCha force-pushed the feat/unit-replays-condition-to-jar-release branch from 9b7a84b to 03b6fea Compare November 13, 2025 21:51
@amkCha amkCha requested a review from DavePearce November 13, 2025 21:51
# Publish release post tests
# ==================================================================
publish-default:
needs: [ build, unit-tests-prague, replay-tests ]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Publishing Ignores Critical Test Failures

The publish-default job waits for unit-tests-prague and replay-tests but not unit-tests-cancun, even though CANCUN tests are defined and run. This means publishing can proceed even if CANCUN tests fail, which contradicts the PR's intent to make releases conditional on all unit and replay tests passing.

Fix in Cursor Fix in Web

Copy link
Collaborator

@DavePearce DavePearce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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.

3 participants