chore: Skip running Redshift xa11y tests - #495
Merged
Merged
Conversation
Signed-off-by: Karthik Bekal Pattathana <133984042+karthikbekalp@users.noreply.github.com>
github-actions
Bot
added
the
waiting-on-maintainers
karthikbekalp
enabled auto-merge (squash)
July 22, 2026 17:55
kavmur
approved these changes
Jul 22, 2026
karthikbekalp
changed the title
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
2 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 was the problem/requirement? (What/Why)
Currently, the Redshift tests are failing in CI.
What was the solution? (How)
Add a temporary skip while we investigate the root cause. (We do have older integration tests that run these Redshift tests now so we are covered).
The current theory is licensing because it needs to checkout both Redshift and Cinema 4D licenses which I think our current licensing infra is not able to run. I'll keep investigating this on my end.
What is the impact of this change?
The tests will continue to pass so that any PRs don't get unnecessarily blocked.
How was this change tested?
Just skipping the tests.
Was this change documented?
Only test and CI change, no documentation updates necessary.
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.