Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-21387][tests] Remove test timeout from DispatcherTest.testNonBlockingJobSubmission and .testInvalidCallDuringInitialization #15343

Closed
wants to merge 1 commit into from

Conversation

tillrohrmann
Copy link
Contributor

The 5s test timeout for the DispatcherTest.testNonBlockingJobSubmission and .testInvalidCallDuringInitialization failed on the CI infrastructure. Therefore, this commit removes these timeouts in order to harden the mentioned tests.

…lockingJobSubmission and .testInvalidCallDuringInitialization

The 5s test timeout for the DispatcherTest.testNonBlockingJobSubmission and .testInvalidCallDuringInitialization failed on the CI
infrastructure. Therefore, this commit removes these timeouts in order to harden the mentioned tests.
@flinkbot
Copy link
Collaborator

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit 4363083 (Tue Mar 23 13:17:46 UTC 2021)

Warnings:

  • No documentation files were touched! Remember to keep the Flink docs up to date!

Mention the bot in a comment to re-run the automated checks.

Review Progress

  • ❓ 1. The [description] looks good.
  • ❓ 2. There is [consensus] that the contribution should go into to Flink.
  • ❓ 3. Needs [attention] from.
  • ❓ 4. The change fits into the overall [architecture].
  • ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.


The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

@flinkbot
Copy link
Collaborator

flinkbot commented Mar 23, 2021

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run travis re-run the last Travis build
  • @flinkbot run azure re-run the last Azure build

Copy link
Contributor

@XComp XComp left a comment

Choose a reason for hiding this comment

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

The reasoning makes sense. I verified your findings in the logs. The change looks good to me. 👍

@tillrohrmann
Copy link
Contributor Author

Thanks for the review @XComp. Merging this PR now.

tillrohrmann added a commit that referenced this pull request Mar 26, 2021
…lockingJobSubmission and .testInvalidCallDuringInitialization

The 5s test timeout for the DispatcherTest.testNonBlockingJobSubmission and .testInvalidCallDuringInitialization failed on the CI
infrastructure. Therefore, this commit removes these timeouts in order to harden the mentioned tests.

This closes #15343.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants