Improve test coverage of BigintGroupByHash and MultiChannelGroupByHash#12613
Merged
sopel39 merged 1 commit intotrinodb:masterfrom May 31, 2022
Merged
Improve test coverage of BigintGroupByHash and MultiChannelGroupByHash#12613sopel39 merged 1 commit intotrinodb:masterfrom
sopel39 merged 1 commit intotrinodb:masterfrom
Conversation
losipiuk
reviewed
May 31, 2022
core/trino-main/src/test/java/io/trino/operator/TestGroupByHash.java
Outdated
Show resolved
Hide resolved
losipiuk
reviewed
May 31, 2022
core/trino-main/src/test/java/io/trino/operator/TestGroupByHash.java
Outdated
Show resolved
Hide resolved
losipiuk
approved these changes
May 31, 2022
sopel39
force-pushed
the
ks/improve_coverage
branch
from
cf8f1ff to
342a58d
Compare
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
Related issues, pull requests, and links
Documentation
( ) 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
( ) No release notes entries required.
( ) Release notes entries required with the following suggested text: