Doctest setup #151
Closed
Doctest setup #151
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ricardoV94, @twiecki I've noticed that since the discrete Markov was merged into main, TestDiscreteMarkovRV is always failing in every single local and origin test run, is someone working on that right now? Because if not then I believe we should disable it to not risk it hiding other bugs (the following tests wouldn't run when this fails) |
twiecki
previously approved these changes
Apr 27, 2023
michaelraczycki
force-pushed
the
doctest_setup
branch
from
914d5e6 to
0631d66
Compare
michaelraczycki
force-pushed
the
doctest_setup
branch
from
0631d66 to
53e153e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A basic doctest setup that builds without errors. So far no tests are detected, so as a task for the future we should add them to all major classes/methods
Related to #145