-
Notifications
You must be signed in to change notification settings - Fork 219
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
Resolve ADTypeCheckContext method ambiguity #2299
Conversation
I guess these ambiguities arise from TuringLang/DynamicPPL.jl#636 which has not been released yet (and therefore currently they show only up in DynamicPPL CI but not in Turing). |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2299 +/- ##
==========================================
- Coverage 83.98% 82.47% -1.51%
==========================================
Files 24 24
Lines 1617 1615 -2
==========================================
- Hits 1358 1332 -26
- Misses 259 283 +24 ☔ View full report in Codecov by Sentry. |
Pull Request Test Coverage Report for Build 10317898020Details
💛 - Coveralls |
Thanks @devmotion, that makes sense. We seem to have an unfortunate case here where a PR that passed tests (#2291) was merged, and then immediately after merging tests on master started to fail (https://github.com/TuringLang/Turing.jl/actions/runs/10281463329/job/28451089388). That's still the failure in this PR too. It's a concurrency problem of some kind, only appears on multithreaded. Haven't dug into it yet. |
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.
Thanks @mhauru!
Merging this since the test failure is on master too and the loss of coverage seems unrelated, and this is holding up the DPPL PR. Need to get to the bottom of the test failure and how it slipped through in the first place though. |
Should fix the issue in TuringLang/DynamicPPL.jl#638. I'm a bit bothered by way the method ambiguity did not come up in Turing's own CI, but only in DPPL's. Also, I think this will fix the issue, but might need to run DPPL's tests to see.