Merge #870

870: Transfer can_inline to subprocess r=KristofferC a=fingolfin

This is meant as an alternative to PR #866 for resolving issue #865

Co-authored-by: Max Horn <max@quendi.de>
Co-authored-by: Kristoffer Carlsson <kristoffer.carlsson@chalmers.se>

src/Operations.jl

@@ -1333,6 +1333,7 @@ function test(ctx::Context, pkgs::Vector{PackageSpec}; coverage=false)
             --color=$(Base.have_color ? "yes" : "no")
             --compiled-modules=$(Bool(Base.JLOptions().use_compiled_modules) ? "yes" : "no")
             --check-bounds=yes
+            --inline=$(Bool(Base.JLOptions().can_inline) ? "yes" : "no")
             --startup-file=$(Base.JLOptions().startupfile == 1 ? "yes" : "no")
             --track-allocation=$(("none", "user", "all")[Base.JLOptions().malloc_log + 1])
             --eval $code

src/Pkg.jl

@@ -150,6 +150,8 @@ passing `coverage=true`. The default behavior is not to run coverage.
 
 The tests are executed in a new process with `check-bounds=yes` and by default `startup-file=no`.
 If using the startup file (`~/.julia/config/startup.jl`) is desired, start julia with `--startup-file=yes`.
+Inlining of functions during testing can be disabled (for better coverage accuracy)
+by starting julia with `--inline=no`.
 """
 const test = API.test