[Flink-12164][tests] Harden JobMasterTest.testJobFailureWhenTaskExecutorHeartbeatTimeout

[ifndef-SleePy]

What is the purpose of the change

• Harden unstable case, JobMasterTest.testJobFailureWhenTaskExecutorHeartbeatTimeout

Brief change log

• Enrich TestingHeartbeatServices, support manually trigger timeout for testing
• Make JobMasterTest.testJobFailureWhenTaskExecutorHeartbeatTimeout not relying on timeout anymore
• Correct invalid format of JobMasterTest

Verifying this change

• This change is already covered by existing tests, such as JobMasterTest

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

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 b3ee3de (Tue Aug 06 16:03:42 UTC 2019)

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.
  • Needs attention by @tillrohrmann [PMC]
• ❓ 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.

Details

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]

CI report:

• ee88127 : FAILURE Build
• f786c67 : FAILURE Build
• 5389b3c : FAILURE Build
• b3ee3de : SUCCESS Build

[ifndef-SleePy]

The Travis building fails due to a known unstable case, see https://issues.apache.org/jira/browse/FLINK-13242

[ifndef-SleePy]

@flinkbot attention @tillrohrmann

[ifndef-SleePy]

Bad luck. Travis building fails due to another unstable case, see https://issues.apache.org/jira/browse/FLINK-9900.
Will re-trigger Travis building.

[ifndef-SleePy]

This PR overrides too much basic logic, I should re-implement it. Close it for now.