-
Notifications
You must be signed in to change notification settings - Fork 6k
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] linux://doc/source/ray-air/examples:gptj_serving
is failing/flaky on master.
#41491
Labels
flaky-tracker
Issue created via Flaky Test Tracker https://flaky-tests.ray.io/
P0
Issues that should be fixed in short order
train
Ray Train Related Issue
Comments
justinvyu
added
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
serve
Ray Serve Related Issue
train
Ray Train Related Issue
flaky-tracker
Issue created via Flaky Test Tracker https://flaky-tests.ray.io/
labels
Nov 29, 2023
8 tasks
can-anyscale
pushed a commit
that referenced
this issue
Nov 30, 2023
This example is consistently flaky, so we should make it non-blocking: #41491 Signed-off-by: Justin Yu <justinvyu@anyscale.com>
anyscalesam
removed
the
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
label
Dec 11, 2023
@justinvyu can we upgrade this to p0 given it's a linux release test and something when it gets to ray210 release we would block correct? |
@anyscalesam Yes let's fix it. I think it's caused by some external change (GPU out of memory error without any code change on our side).
|
anyscalesam
added
P0
Issues that should be fixed in short order
and removed
P1
Issue that should be fixed within a few weeks
labels
Jan 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
flaky-tracker
Issue created via Flaky Test Tracker https://flaky-tests.ray.io/
P0
Issues that should be fixed in short order
train
Ray Train Related Issue
....
Generated from flaky test tracker. Please do not edit the signature in this section.
DataCaseName-linux://doc/source/ray-air/examples:gptj_serving-END
....
The text was updated successfully, but these errors were encountered: