apache/beam

Suppress tracebacks on failure-catching tests

Open

#18,935 opened on Jun 3, 2022

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Java (4,097 forks)batch import
P3bugcoregood first issuepython

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (PR metrics pending)

Description

Our tests of assert_that (e.g. in apache_beam.runners.portability.fn_api_runner_test) dump the expected "error" to stdout making our tests noisy (and they look like failures). It'd be good to suppress these in tests (while making sure things are still properly logged on workers. 

There are probably other tests of similar nature. 

Imported from Jira BEAM-4012. Original Jira may contain additional context. Reported by: robertwb.

Contributor guide

Research direction
Identify test files that dump tracebacks on expected failures and use logging suppression or mocking to quiet them while preserving worker logging.
Tech stack
javapython
Domain
testingbackend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonJavaApache Beam testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60