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

[Task]: Re-enable schedule trigger for PostCommit Java IO Performance Tests #30787

Closed
16 tasks
volatilemolotov opened this issue Mar 28, 2024 · 1 comment · Fixed by #31024
Closed
16 tasks

Comments

@volatilemolotov
Copy link
Contributor

What needs to happen?

We need to re-enable schedule trigger for PostCommit Java IO Performance Tests after the 2.56 release.

The change is done in this PR #30751

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

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: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@damccorm
Copy link
Contributor

I have #31024 to fix this once the 2.56 release is out

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

Successfully merging a pull request may close this issue.

2 participants