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

Enable FutureWarnings and DeprecationWarnings as errors in cugraph #4271

Closed

Conversation

mroeschke
Copy link
Contributor

Follow up to #4223 and rapidsai/build-planning#26, cugraph tests will fail if a FutureWarning or DeprecationWarning is raised

@mroeschke mroeschke requested a review from a team as a code owner March 22, 2024 20:29
@mroeschke mroeschke marked this pull request as draft March 22, 2024 20:29
@mroeschke mroeschke changed the title Enable FutureWarnings and Deprecations as errors in cugraph Enable FutureWarnings and DeprecationWarnings as errors in cugraph Mar 22, 2024
@BradReesWork BradReesWork added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Apr 15, 2024
rapids-bot bot pushed a commit that referenced this pull request May 8, 2024
xref #4271

`chunksize` was deprecated in favor of `blocksize`

Also removed an unsupported `chunksize` in a `cudf.read_csv` call

Authors:
  - Matthew Roeschke (https://github.com/mroeschke)

Approvers:
  - Don Acosta (https://github.com/acostadon)
  - Rick Ratzel (https://github.com/rlratzel)

URL: #4379
rapids-bot bot pushed a commit that referenced this pull request May 11, 2024
Broken off from #4271

Appears this was deprecated in favor of `induced_subgraph`

Authors:
  - Matthew Roeschke (https://github.com/mroeschke)

Approvers:
  - Rick Ratzel (https://github.com/rlratzel)

URL: #4386
rapids-bot bot pushed a commit that referenced this pull request May 11, 2024
xref #4271

For methods/parameters that are deprecated, ensures the doctests will pass if `FutureWarning` or `DeprecationWarning` are made as errors

Authors:
  - Matthew Roeschke (https://github.com/mroeschke)

Approvers:
  - Rick Ratzel (https://github.com/rlratzel)

URL: #4380
@mroeschke
Copy link
Contributor Author

closing in favor of #4415

@mroeschke mroeschke closed this May 14, 2024
@mroeschke mroeschke deleted the test/futurewarnings/errors branch May 14, 2024 00:37
rapids-bot bot pushed a commit that referenced this pull request May 20, 2024
…4415)

Supersedes #4271

There are some tests and internal usages of APIs that emit these warnings still. I don't know the best way to handle these warnings, but this PR ensures that _new_ `FutureWarning`s and `DeprecationWarning`s will raise an error in the CI

Authors:
  - Matthew Roeschke (https://github.com/mroeschke)

Approvers:
  - Rick Ratzel (https://github.com/rlratzel)

URL: #4415
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement / enhancement to an existing function non-breaking Non-breaking change python
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants