apache / apache/beam

TestDataflowRunner should log explicitly when it is interruped

Open
#19,443 0 comments 0 reactions 0 assignees View on GitHub
bug dataflow P3 runners
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

Right now, one is left to deduce that a test was interrupted, where a well placed log line around https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/TestDataflowRunner.java#L163 would make it obvious. It won't be spammy, as things are about to terminate if this ever happens.

Imported from Jira [BEAM-6893](https://issues.apache.org/jira/browse/BEAM-6893). Original Jira may contain additional context.
Reported by: kenn.

Contributor guide

Open the contributing guide

Research direction

Open runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/TestDataflowRunner.java around line 163 and trace how interruption is handled. Add an explicit log at that point so the interrupted test is obvious before termination. Done means the interruption path emits a clear, non-spammy log message.

Written by the indexing model from the issue text.

Assessment

Tech stack
google-cloud, java
Domain
cloud, testing
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.