-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Eliminate warning responsible for nondeterministic test failure #10531
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
base: master
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #10531 +/- ##
==========================================
- Coverage 86.11% 85.09% -1.02%
==========================================
Files 496 510 +14
Lines 33655 35962 +2307
==========================================
+ Hits 28981 30602 +1621
- Misses 4674 5360 +686 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
akihironitta
left a 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.
Hi @drivanov, thank you for sending a fix here. How can I reproduce the issue this PR is trying to fix? I ran the test case quite tens of times in master, but I cannot reproduce it.
|
Hi @akihironitta: Run this test with On systems with A100 or H200 GPU cards, the observed failure rate varies between 2% and 10%. For instance, it's what I see: |
The
test_to_hetero_lazy_cudaoccasionally triggers the following warning:This warning can nondeterministically escalate into an AttributeError, causing the test to fail:
The root cause is that the synthetic
FakeHeteroDatasetincludes a node type (v0) that never appears as a destination in any edge type, so its representation is never updated. This fix ensures that all node types participate as destinations (via self-loop edges), preventing the warning and stabilizing the test.Solution originated from ChatGPT guidance.