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

[Data] Mark chaos_pipelined_ingestion_1500_gb_15_windows as unstable #35609

Merged
merged 1 commit into from
May 23, 2023

Conversation

amogkam
Copy link
Contributor

@amogkam amogkam commented May 22, 2023

Screen Shot 2023-05-22 at 9 54 55 AM

chaos_pipelined_ingestion_1500_gb_15_windows has been sporadically failing for a few weeks now due to object not found issues. As the initial flakiness started a few weeks ago, it's too late to bisect and revert. Instead, we mark as unstable and will have to forward fix/remove the test.

Closes #35523

Why are these changes needed?

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: amogkam <[email protected]>
@amogkam amogkam merged commit cfe5dad into ray-project:master May 23, 2023
2 checks passed
@amogkam amogkam deleted the mark-unstable branch May 23, 2023 03:04
scv119 pushed a commit to scv119/ray that referenced this pull request Jun 16, 2023
…ay-project#35609)

Signed-off-by: amogkam <[email protected]>

chaos_pipelined_ingestion_1500_gb_15_windows has been sporadically failing for a few weeks now due to object not found issues. As the initial flakiness started a few weeks ago, it's too late to bisect and revert. Instead, we mark as unstable and will have to forward fix/remove the test.
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
…ay-project#35609)

Signed-off-by: amogkam <[email protected]>

chaos_pipelined_ingestion_1500_gb_15_windows has been sporadically failing for a few weeks now due to object not found issues. As the initial flakiness started a few weeks ago, it's too late to bisect and revert. Instead, we mark as unstable and will have to forward fix/remove the test.

Signed-off-by: e428265 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Data] chaos_pipelined_ingestion_1500_gb_15_windows.aws failing
2 participants