Temporarily disable kudu tests from running in CI#11313
Merged
hashhar merged 1 commit intotrinodb:masterfrom Mar 4, 2022
Merged
Temporarily disable kudu tests from running in CI#11313hashhar merged 1 commit intotrinodb:masterfrom
hashhar merged 1 commit intotrinodb:masterfrom
Conversation
Flakiness is happening often and impacting other PRs. See issue here: trinodb#11203
hashhar
approved these changes
Mar 4, 2022
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.
Description
Flakiness is happening often and impacting other PRs.
Related issues, pull requests, and links
#11203
#11264
Disabling due to conversation here: #11286 (comment)
Unfortunately the flakiness occurs during creating a table and then subsequently opening it. Because this flakiness can occur in almost any integration test (eg: loading TPCH test data) disabling the whole suite makes more sense.
Documentation
(X ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(X ) No release notes entries required.
( ) Release notes entries required with the following suggested text: