Skip to content

Conversation

@kennknowles
Copy link
Member

This sickbays the test until it can be diagnosed, as it is very flaky and increased timeout is not effective.

This also reverts a prior erroneous "fix".


Follow this checklist to help us incorporate your contribution quickly and easily:

  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- --- --- --- ---
Java Build Status Build Status Build Status Build Status Build Status Build Status Build Status Build Status
Python Build Status --- Build Status
Build Status
Build Status --- --- ---

This reverts commit 6c20192.

This timeout increase was made to the wrong test method. Further
investigation shows that increased timeout does not help, as the issue
appears to be a full deadlock.
@kennknowles
Copy link
Member Author

The flakes in https://issues.apache.org/jira/browse/BEAM-6130 and https://issues.apache.org/jira/browse/BEAM-6129 struck here. I would prefer not to fix all flakes in one PR, but that would seem the only way to reliable green. I am going to make the call and merge this, moving on to the others separately.

@kennknowles kennknowles merged commit ad150c1 into apache:master Nov 27, 2018
@kennknowles kennknowles deleted the sickbay-UnboundedSourceWrapperTest branch November 27, 2018 05:06
import org.slf4j.LoggerFactory;

/** Tests for {@link UnboundedSourceWrapper}. */
@RunWith(Enclosed.class)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't this disable all tests of the nested classes? Was this intended?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I could have left this in place. This was a line from my earlier PR. Before that time, this was never there. It turns out that many test runners will find the inner classes anyhow. But I do think this should be restored.

@mxm
Copy link
Contributor

mxm commented Nov 27, 2018

Thank you for taking care of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants