8385891: Introduce a test for GZIPInputStream whose underlying stream is a blocking InputStream#31369
Open
jaikiran wants to merge 1 commit into
Open
8385891: Introduce a test for GZIPInputStream whose underlying stream is a blocking InputStream#31369jaikiran wants to merge 1 commit into
jaikiran wants to merge 1 commit into
Conversation
… is a blocking InputStream
|
👋 Welcome back jpai! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
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
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.
Can I please get a review of this change which proposes to introduce a new jtreg test to cover the case where the underlying
InputStreamof aGZIPInputStreamblocks?This test should help us catch any future regressions like the one reported recently in https://bugs.openjdk.org/browse/JDK-8377896. In fact, this test when run against a JDK version which has the changes from http://bugs.openjdk.org/browse/JDK-7036144, does indeed reproduce the JDK-8377896 issue.
The test passes in the current mainline.
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/31369/head:pull/31369$ git checkout pull/31369Update a local copy of the PR:
$ git checkout pull/31369$ git pull https://git.openjdk.org/jdk.git pull/31369/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 31369View PR using the GUI difftool:
$ git pr show -t 31369Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/31369.diff
Using Webrev
Link to Webrev Comment