test: Run integration tests across Cinema 4D versions (2024,2025,2026) - #514
Closed
karthikbekalp wants to merge 2 commits into
Closed
test: Run integration tests across Cinema 4D versions (2024,2025,2026)#514karthikbekalp wants to merge 2 commits into
karthikbekalp wants to merge 2 commits into
Conversation
Signed-off-by: Karthik Bekal Pattathana <133984042+karthikbekalp@users.noreply.github.com>
github-actions
Bot
added
the
waiting-on-maintainers
Contributor
Author
|
Wrong target branch: #515 |
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.
What was the problem/requirement? (What/Why)
We need to run integration tests on all the versions of Cinema 4d that we currently support and not just 2026.
What was the solution? (How)
Updated the tests to run on all the versions that we support i.e. 2024 to 2026.
We still have issues with Redshift tests failing because of a Maxon bug so marked those tests as XFAIL so that even if it flakes it does not break the workflow.
What is the impact of this change?
We have higher coverage and make sure our changes are backwards compatible.
How was this change tested?
Ran the tests here: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/actions/runs/31415004267/job/93541820105
Was this change documented?
No documentation changes required. Only test changes.
Is this a breaking change?
No.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.