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

CI test linux://python/ray/tests:test_channel is consistently_failing #45264

Closed
can-anyscale opened this issue May 11, 2024 · 26 comments · Fixed by #45297
Closed

CI test linux://python/ray/tests:test_channel is consistently_failing #45264

can-anyscale opened this issue May 11, 2024 · 26 comments · Fixed by #45297
Assignees
Labels
bug Something that is supposed to be working; but isn't ci-test core Issues that should be addressed in Ray Core flaky-tracker Issue created via Flaky Test Tracker https://flaky-tests.ray.io/ ray-test-bot Issues managed by OSS test policy stability triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@can-anyscale
Copy link
Collaborator

CI test linux://python/ray/tests:test_channel is consistently_failing. Recent failures:
- https://buildkite.com/ray-project/postmerge/builds/4400#018f6537-f627-42c9-a037-195010e2b35c
- https://buildkite.com/ray-project/postmerge/builds/4400#018f6537-f623-449e-a07b-e99c4a177a24

DataCaseName-linux://python/ray/tests:test_channel-END
Managed by OSS Test Policy

@can-anyscale can-anyscale added bug Something that is supposed to be working; but isn't ci-test core Issues that should be addressed in Ray Core flaky-tracker Issue created via Flaky Test Tracker https://flaky-tests.ray.io/ ray-test-bot Issues managed by OSS test policy stability triage Needs triage (eg: priority, bug/not-bug, and owning component) weekly-release-blocker Issues that will be blocking Ray weekly releases labels May 11, 2024
@can-anyscale
Copy link
Collaborator Author

This test is now considered as flaky because it has been failing on postmerge for too long. Flaky tests do not run on premerge.

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

blame to 79f3995

@can-anyscale
Copy link
Collaborator Author

Blamed commit: 79f3995 found by bisect job https://buildkite.com/ray-project/release-tests-bisect/builds/1124

@can-anyscale
Copy link
Collaborator Author

This test is now considered as flaky because it has been failing on postmerge for too long. Flaky tests do not run on premerge.

@stephanie-wang stephanie-wang removed the weekly-release-blocker Issues that will be blocking Ray weekly releases label May 13, 2024
stephanie-wang added a commit that referenced this issue May 13, 2024
Fixes test that was broken due a hidden merge conflict between #45092 and #45119.
Related issue number

Closes #45264.

Signed-off-by: Stephanie Wang <[email protected]>
@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

@can-anyscale
Copy link
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't ci-test core Issues that should be addressed in Ray Core flaky-tracker Issue created via Flaky Test Tracker https://flaky-tests.ray.io/ ray-test-bot Issues managed by OSS test policy stability triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants