Add a workflow to trigger the system tests - #23
Merged
Merged
Conversation
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
1 participant
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.
Adds a workflow to trigger the system tests (
fmi-runnertest suite) when adding/re-adding thetrigger-system-testslabel.Note that, due to the way we install Python packages via the requirements.txt, for PRs from forks (only), the workflow will fail as it will not be able to find the commit from the fork on the main repository. I am not sure how to further improve that, but see precice/tutorials#858 for details. For this reason, I am not passing the (unused)
FMI_RUNNER_PR.A workaround in the case of a PR from a fork is to push a copy of the respective branch in the main repository and manually trigger the system tests.
Still, for PRs from the main repository, this should work as expected.