-
Notifications
You must be signed in to change notification settings - Fork 479
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
UndefVarError when using with Distributed #1848
Comments
I believe |
Yes, In the bigger picture, I would like to have a demo (that is included in the docs) tested by doctests. I didn't use |
Ah, you had already figured that out, didn't read the issue fully, sorry. There is no way to turn it off, maybe you can wrap the block in
but I have not tried this.
The build fails if you have errors in |
This works partially. The code does not fail, but the output still is
Yes, the build fails if an error occurs, but what if I screwed up and the example succeeds but does no longer return what I explain in the surrounding documentation? Putting every output in a separate variable (which I could not I just encountered the next problem: when using an
but if I hit
and the docs then contain
as the result of that code example. |
At SciML, we also have issues with the |
One idea would be to shadow the |
Or for this specific example you could just shadow it with a no-op macro. |
For my use case, performance is not critical and over-subscription is fine. I would much rather have the code properly executed and thus tested. |
How do I document/test examples that involve
Distributed
? Is it somehow possible to deactivate the sandboxing, such that@everywhere
works as expected?Example
Consider the following
src/index.md
:Building the docs yields this:
The text was updated successfully, but these errors were encountered: