fix flaky test, remove high tolerance #7567
Merged
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.
Description
The multi-output GP test was flaky. Turns out that it was lucky that it was passing occasionally. It was testing whether two GP implementations were correct when they were subtly different.
pm.gp.Latent.conditional
was conditioning on the original gpf
, andpm.gp.Marginal.conditional
was conditioning on the observed datay
. The fix is to conditionpm.gp.Latent.conditional
ony
also in the test.Related Issue
tests/gp/test_gp.py::TestMarginalVsLatent::testLatentMultioutput
#7531Checklist
Type of change
📚 Documentation preview 📚: https://pymc--7567.org.readthedocs.build/en/7567/