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
[GraphBolt] Improving ondisk_dataset
tests.
#7052
base: master
Are you sure you want to change the base?
Conversation
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
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.
I think it's better to explicitly capture warnings directly in the testcase. and check if we really need to enable include_original_edge_id
or remove edge feature before adding such capture. We only capture for those where warning is inevitable.
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
@Rhett-Ying : Sorry, I'm not sure I understand what you're talking about. We already have similar captures of that warning here and here. They are generated only for Note that I'm not simply suppressing this warning even though it won't be generated. With the following lines:
the program expects that this warning will be generated, therefore it should be considered as inevitable Moreover, if the program expects to see, but won't see, this warning for some test, that test will fail with the following error message:
I just got it with the following changes:
I made to |
@drivanov Sorry for the vagueness. What I mean is if we mean to verify such warning is thrown or inevitable, then directly wrap with |
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
@Rhett-Ying : I have implemented the changes you suggested. |
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.
please fix test failure running on Windows.
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
this PR could be abandoned if #7110 is merged. |
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Description
The goal of this PR is to resolve the following 24 warnings that appear when running tests from
test_ondisk_dataset.py
:To achieve this goal, I created and started using a new local function `_on_disk_dataset(...) which uses the method already used several times in this file:
Checklist
Please feel free to remove inapplicable items for your PR.
Changes