Fix cloud database tests calling the removed tools/run-tests.ps1 - #5887
Merged
Conversation
The cloud-database-tests workflow still invoked tools/run-tests.ps1, which 9ceb32b deleted when ci.yml moved to Particular/run-tests-action. The workflow was never exercised before the 6.21.0 tag, so every cloud-tests job in the release run failed with 'The term ./tools/run-tests.ps1 is not recognized'. Use the same action ci.yml uses, passing both suites via its projects input.
mauroservienti
approved these changes
Sep 11, 2026
rbev
approved these changes
Sep 11, 2026
johnsimons
approved these changes
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Every
cloud-testsjob in the 6.21.0 release run failed at the Run tests step:cloud-database-tests.yml(added in #5863) still invokestools/run-tests.ps1, but 9ceb32b deleted that script on 2026-09-07 whenci.ymlmoved toParticular/run-tests-action(which grew aprojectsinput for exactly this purpose). The two changes never conflicted in git because #5863 introduced a new file, and the cloud workflow only runs viaworkflow_callfrom the release workflow or manual dispatch, so the reference was never exercised until the tag was pushed.Fix
Call
Particular/run-tests-action@v1.9.0the same wayci.ymldoes, passing the persistence and acceptance projects via theprojectsinput (semicolon-delimited, matchingci.yml) withmax-parallel: 2.Impact of the failure
The release itself is unaffected:
windows-installers,containersanddb-containerare independent jobs with noneedsoncloud-tests, and all succeeded. Only the cloud database verification did not run for 6.21.0. Once merged, the workflow can be re-run for that tag viaworkflow_dispatchif that coverage is wanted.