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 windows://python/ray/serve/tests:test_deploy_2 is consistently_failing #48289

Closed
can-anyscale opened this issue Oct 28, 2024 · 5 comments
Assignees
Labels
bug Something that is supposed to be working; but isn't ci-test flaky-tracker Issue created via Flaky Test Tracker https://flaky-tests.ray.io/ ray-test-bot Issues managed by OSS test policy serve Ray Serve Related Issue stability triage Needs triage (eg: priority, bug/not-bug, and owning component) weekly-release-blocker Issues that will be blocking Ray weekly releases

Comments

@can-anyscale
Copy link
Collaborator

CI test windows://python/ray/serve/tests:test_deploy_2 is consistently_failing. Recent failures:
- https://buildkite.com/ray-project/postmerge/builds/6696#0192d1c2-1c72-481f-b833-645b693e1d40
- https://buildkite.com/ray-project/postmerge/builds/6696#0192d187-6593-48f0-86e9-49e07ade000b

DataCaseName-windows://python/ray/serve/tests:test_deploy_2-END
Managed by OSS Test Policy

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

Blame 90e6e72

@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.

@edoakes edoakes closed this as completed Oct 28, 2024
@can-anyscale
Copy link
Collaborator Author

@can-anyscale can-anyscale reopened this Oct 29, 2024
@can-anyscale
Copy link
Collaborator Author

Jay-ju pushed a commit to Jay-ju/ray that referenced this issue Nov 5, 2024
JP-sDEV pushed a commit to JP-sDEV/ray that referenced this issue Nov 14, 2024
…t level" (ray-project#48292)

Reverts ray-project#48223

Broke ray-project#48289 so revert to
unblock the release.
Signed-off-by: JP-sDEV <jon.pablo80@gmail.com>
mohitjain2504 pushed a commit to mohitjain2504/ray that referenced this issue Nov 15, 2024
…t level" (ray-project#48292)

Reverts ray-project#48223

Broke ray-project#48289 so revert to
unblock the release.

Signed-off-by: mohitjain2504 <mohit.jain@dream11.com>
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 flaky-tracker Issue created via Flaky Test Tracker https://flaky-tests.ray.io/ ray-test-bot Issues managed by OSS test policy serve Ray Serve Related Issue stability triage Needs triage (eg: priority, bug/not-bug, and owning component) weekly-release-blocker Issues that will be blocking Ray weekly releases
Projects
None yet
Development

No branches or pull requests

3 participants