kubernetes/kubernetes

k8s.io/apiserver/pkg/util: proxy TestStreamTranslator_TTYResizeChannel failing in `pull-kubernetes-unit`

Open

#130018 opened on Feb 6, 2025

View on GitHub
 (30 comments) (0 reactions) (1 assignee)Go (122,268 stars) (43,066 forks)batch import
help wantedkind/flakepriority/backlogsig/api-machinerytriage/accepted

Description

Which jobs are flaking?

pull-kubernetes-unit

Which tests are flaking?

TestStreamTranslator_TTYResizeChannel

Since when has it been flaking?

Noticed the failure in https://github.com/kubernetes/kubernetes/pull/129993

Testgrid link

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/129993/pull-kubernetes-unit/1887599657052278784

Reason for failure (if possible)

No response

Anything else we need to know?

No response

Relevant SIG(s)

/sig api-machinery

Contributor guide

Tech stack
go
Domain
backendtesting
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingFamiliarity with KubernetesUnderstanding of flaky tests
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the flaky test TestStreamTranslator TTYResizeChannel in k8s.io/apiserver/pkg/util. Start by examining the test file for recent changes that might have introduced instability. Look at the Prow build log linked in the issue for specific failure messages. The PR #129993 may contain related modifications; check its diff and comments. Consider if the flake is due to timing issues or resource constraints. Reproduce locally using `make test` with focus on the failing test. Reach out to the SIG API Machinery for insights on known issues.