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

The PostCommit Sickbay Python job is flaky #30882

Closed
github-actions bot opened this issue Apr 7, 2024 · 5 comments · Fixed by #33214
Closed

The PostCommit Sickbay Python job is flaky #30882

github-actions bot opened this issue Apr 7, 2024 · 5 comments · Fixed by #33214

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Apr 7, 2024

The PostCommit Sickbay Python is failing over 50% of the time
Please visit https://github.com/apache/beam/actions/workflows/beam_PostCommit_Sickbay_Python.yml?query=is%3Afailure+branch%3Amaster to see the logs.

@damccorm
Copy link
Contributor

damccorm commented Apr 8, 2024

This is expected, but I'm going to keep it open to avoid automation reopening at P1. Longer term it would be good to exclude this from the automation

@kennknowles
Copy link
Member

How about we delete this suite? I don't think we get any benefit from running it.

@damccorm
Copy link
Contributor

I agree

@damccorm
Copy link
Contributor

We could also consider not running it on a schedule, but allowing manual runs

@github-actions github-actions bot added this to the 2.59.0 Release milestone Aug 20, 2024
@github-actions github-actions bot reopened this Aug 23, 2024
Copy link
Contributor Author

Reopening since the workflow is still flaky

@damccorm damccorm removed this from the 2.59.0 Release milestone Aug 23, 2024
@kennknowles kennknowles self-assigned this Nov 25, 2024
@github-actions github-actions bot added this to the 2.62.0 Release milestone Nov 25, 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