-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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_streaming_generator_regression is flaky #43852
Comments
This one was opened due to a bug in CI (it fails only one so it's not that flaky), let's close to see if it happens again |
Test passed on latest run: https://buildkite.com/ray-project/postmerge/builds/3505#018e3b5f-2402-4512-8bd2-b7dd32e7404d |
CI test linux://python/ray/tests:test_streaming_generator_regression is flaky. Recent failures: DataCaseName-linux://python/ray/tests:test_streaming_generator_regression-END |
@can-anyscale test is failing b/c of filename:
--- UPDATED I stand corrected. It indeed failed to upload artifacts due to the length of the test name, but the test indeed fails (it's hanging) |
…44197) When a streaming generator task is cancelled, we should mark the end of the stream at the caller's current pointer into the stream. Otherwise, if we receive out-of-order item reports, we may end up hanging, because the cancelled task will never report the intermediate items. We may end up dropping some values that were already reported, but this is OK since the user already cancelled the task. Closes #43852. Note: #44257 is also enough to make the relevant flaky test stable, probably because it makes it less likely to produce out-of-order item reports. Meanwhile, this PR addresses the root cause of the flaky test, i.e. out-of-order item reports during task cancellation. --------- Signed-off-by: Stephanie Wang <[email protected]>
…ay-project#44197) When a streaming generator task is cancelled, we should mark the end of the stream at the caller's current pointer into the stream. Otherwise, if we receive out-of-order item reports, we may end up hanging, because the cancelled task will never report the intermediate items. We may end up dropping some values that were already reported, but this is OK since the user already cancelled the task. Closes ray-project#43852. Note: ray-project#44257 is also enough to make the relevant flaky test stable, probably because it makes it less likely to produce out-of-order item reports. Meanwhile, this PR addresses the root cause of the flaky test, i.e. out-of-order item reports during task cancellation. --------- Signed-off-by: Stephanie Wang <[email protected]>
Test passed on latest run: https://buildkite.com/ray-project/postmerge/builds/3752#018e8226-56c1-485e-8123-d321f80b8b94 |
CI test linux://python/ray/tests:test_streaming_generator_regression is flaky. Recent failures:
- https://buildkite.com/ray-project/postmerge/builds/3402#018e20bd-8ad0-4db6-86a9-ea7eeb68d97e
DataCaseName-linux://python/ray/tests:test_streaming_generator_regression-END
Managed by OSS Test Policy
The text was updated successfully, but these errors were encountered: