Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Allow cugraph-nx to run networkx tests for nx versions 3.0, 3.1, and 3.2 #3808
Allow cugraph-nx to run networkx tests for nx versions 3.0, 3.1, and 3.2 #3808
Changes from all commits
8b4ef6d
bba78c0
28faf52
544b659
a04883a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(this is also a comment for all of
on_start_tests()
. No action for this PR beyond a potentialFIXME
if we like it.)I'm assuming many backends will have potentially lengthy
on_start_tests()
implementations like this which use basically the same pattern and need frequent modification as the backends evolve to pass more tests.I wonder if we could add a utility function to networkx which allows a backend developer to simply pass the incoming items and a YAML string and have them marked appropriately. The YAML could make it easy to define xfail messages for specific tests and nx versions, making these functions almost purely declarative and easier to read and maintain:
The YAML could be inline like above, or in a separate file that's more discoverable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that sounds nice; we could look into cleaning this up and making it easier for any backend to mark tests as xfail.
This seems pretty low priority for now--we'll see if I/we get frustrated by fiddling with this as we add more algorithms, and maybe we'll get motivated to make it better.