# Is it possible to run a cleanup code after a jldoctest block has been evaluated?

**URL:** <https://discourse.julialang.org/t/is-it-possible-to-run-a-cleanup-code-after-a-jldoctest-block-has-been-evaluated/44999>\
**Category:** General Usage\
**Tags:** question\
**Created:** [August 15, 2020, 4:31pm UTC](https://discourse.julialang.org/t/is-it-possible-to-run-a-cleanup-code-after-a-jldoctest-block-has-been-evaluated/44999 "2020-08-15T16:31:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jishnub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jishnub/32/33620_2.png) [@jishnub](https://discourse.julialang.org/u/jishnub)\
**Post date:** [August 15, 2020, 4:31pm UTC](https://discourse.julialang.org/t/is-it-possible-to-run-a-cleanup-code-after-a-jldoctest-block-has-been-evaluated/44999/1 "2020-08-15T16:31:33Z")

</div>

Documenter allows the inclusion of setup codes for a `jldoctest` section. Is there something analogous that may be run once a block has finished running, sort of a clean-up code?

For example, I’m looking for something like `addprocs(2)` in the setup and `rmprocs(workers())` in the clean-up.