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

[Failing Test]: #33819

Closed
4 of 17 tasks
lalitssonawane opened this issue Jan 31, 2025 · 1 comment
Closed
4 of 17 tasks

[Failing Test]: #33819

lalitssonawane opened this issue Jan 31, 2025 · 1 comment

Comments

@lalitssonawane
Copy link

What happened?

No response

Issue Failure

Failure: Test is flaky

Issue Priority

Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@damccorm
Copy link
Contributor

Hey @lalitssonawane it looks like you didn't include the information needed to debug this issue. In general, we now have automated detection of flaky/failing tests, though, so there is a good chance the suite you're running into already has an associated issue.

I'm closing this issue, feel free to open a new issue with more details if needed though

@github-actions github-actions bot added this to the 2.63.0 Release milestone Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants