staticdata: fix assert from partially disabled native code #53439

vtjnash · 2024-02-22T18:51:15Z

As @vchuravy pointed out in #52123 (comment), this should fix the assertion failure that has been plaguing the Pkg tests

vchuravy · 2024-02-22T19:25:09Z

src/staticdata.c

@@ -3768,8 +3768,11 @@ JL_DLLEXPORT jl_value_t *jl_restore_package_image_from_file(const char *fname, j

    jl_image_t pkgimage = jl_init_processor_pkgimg(pkgimg_handle);

-    if (ignore_native){
-        memset(&pkgimage.fptrs, 0, sizeof(pkgimage.fptrs));
+    if (ignore_native) {


Should we just remove ignore_native and move this instead into _tryrequire_from_serialized here

julia/base/loading.jl

Line 1805 in a96726b

# then load the file

vchuravy

We can do cleanup of ignore_native later, but this is the minimal change for backporting.

IanButterworth · 2024-02-22T21:05:48Z

src/staticdata.c

+        // The easiest way to do that is to disable it in all of them.
+        jl_options.use_sysimage_native_code = JL_OPTIONS_USE_SYSIMAGE_NATIVE_CODE_NO;


Don't let me hold this up, but I don't quite understand what this does and how setting a sysimage flag relates to pkgimage usage.. Will this still allow pkgimages to be used by any packages, most importantly stdlibs like Pkg which are dead slow without pkgimages..

This essentially turns off native code for all images loaded after this moment (including the current one)

In #53373 this option was fixed for pkgimages (where when the sysimage is loaded without native code, pkgimages can use native code either)

IIUC we load the sysimg and all dependency with native code enabled and once we see the first cache file with ignore_native all subsequent cache files can't use native code, since they might point to images that were loaded without native code.

We could be less discriminate if we could prove that there is no overlap in the cached code.

As an example of a slightly problematic issue it is now order dependent if we use native code or not.

using Test # with native code using MyPackage # disables native code

But

using MyPackage # disables native code using Test # without native code

Since we can't know that a code instance is not duplicated between MyPackage and Test, and it depends on which one we load first.

So this generally means that we might ignore the native code of test dependencies, but we will use the native code of actual dependencies.

LilithHafner · 2024-02-23T23:44:24Z

I'm seeing a 4–5x regression in package CI times from this PR.

I CI ran on nightly in 1:27, 1:58, 2:01 on Ubuntu, Mac, Windows nightly Julia Version 1.12.0-DEV.63 Commit 923fe2d (2024-02-23 08:19 UTC)
https://github.com/LilithHafner/Chairmarks.jl/actions/runs/8022715128/job/21917869776

The next commit to my repo (which was an NFC commit) ran on Julia Version 1.12.0-DEV.64 Commit 6cbed31 (2024-02-23 16:16 UTC) in 7:22, 7:35, 7:53.
https://github.com/LilithHafner/Chairmarks.jl/actions/runs/8023817559/job/21921072527

All subsequent nightly CI runs on my repo are slow, and all non-nightly CI runs are fast (both before and after that commit).

IanButterworth · 2024-02-24T00:02:28Z

Moving the main package load to the end of the loads doesn't fix this regression.
LilithHafner/Chairmarks.jl#17

Are we sure that this doesn't propagate to deps also?

LilithHafner · 2024-02-24T00:28:41Z

Pkg.jl tests all timed out when running on this commit Julia Version 1.12.0-DEV.64 Commit 6cbed31 (2024-02-23 16:16 UTC)

https://github.com/JuliaLang/Pkg.jl/actions/runs/8023442598/job/21919915633

Despite succeeding on the same package content in the PR's checks before merge on the commit Julia Version 1.12.0-DEV.63 Commit 923fe2d (2024-02-23 08:19 UTC)

https://github.com/JuliaLang/Pkg.jl/actions/runs/8022722320/job/21917673112

This is neither spurious nor confined to a single package.

…53439)" This reverts commit 6cbed31.

vtjnash · 2024-02-24T00:33:40Z

Are we sure that this doesn't propagate to deps also?

yes, we are pretty sure it cannot affects things in the past

vtjnash · 2024-02-24T00:34:35Z

That said, some packages spawn a lot of subprocesses, and this probably could affect those

LilithHafner · 2024-02-24T01:34:40Z

I can reproduce the performance regression (15 seconds -> 6 mins) locally when deleting all non-aqua tests. Here is a stack frame from interrupting it

(Chairmarks) pkg> test
     Testing Chairmarks
      Status `/tmp/jl_ytpeXk/Project.toml`
  [4c88cf16] Aqua v0.8.4
  [0ca39b1e] Chairmarks v0.2.1 `~/.julia/dev/Chairmarks`
  [10745b16] Statistics v1.11.1
  [44cfe95a] Pkg v1.11.0
  [de0858da] Printf v1.11.0
  [8dfed614] Test v1.11.0
      Status `/tmp/jl_ytpeXk/Manifest.toml`
  [4c88cf16] Aqua v0.8.4
  [0ca39b1e] Chairmarks v0.2.1 `~/.julia/dev/Chairmarks`
  [34da2185] Compat v4.13.0
  [10745b16] Statistics v1.11.1
  [0dad84c5] ArgTools v1.1.2
  [56f22d72] Artifacts v1.11.0
  [2a0f44e3] Base64 v1.11.0
  [ade2ca70] Dates v1.11.0
  [f43a241f] Downloads v1.6.0
  [7b1f6079] FileWatching v1.11.0
  [b77e0a4c] InteractiveUtils v1.11.0
  [b27032c2] LibCURL v0.6.4
  [76f85450] LibGit2 v1.11.0
  [8f399da3] Libdl v1.11.0
  [37e2e46d] LinearAlgebra v1.11.0
  [56ddb016] Logging v1.11.0
  [d6f4376e] Markdown v1.11.0
  [ca575930] NetworkOptions v1.2.0
  [44cfe95a] Pkg v1.11.0
  [de0858da] Printf v1.11.0
  [9a3f8284] Random v1.11.0
  [ea8e919c] SHA v0.7.0
  [9e88b42a] Serialization v1.11.0
  [f489334b] StyledStrings v1.11.0
  [fa267f1f] TOML v1.0.3
  [a4e569a6] Tar v1.10.0
  [8dfed614] Test v1.11.0
  [cf7118a7] UUIDs v1.11.0
  [4ec0a83e] Unicode v1.11.0
  [e66e0078] CompilerSupportLibraries_jll v1.1.0+0
  [deac9b47] LibCURL_jll v8.6.0+0
  [e37daf67] LibGit2_jll v1.7.1+0
  [29816b5a] LibSSH2_jll v1.11.0+1
  [c8ffd9c3] MbedTLS_jll v2.28.6+0
  [14a3606d] MozillaCACerts_jll v2023.1.10
  [4536629a] OpenBLAS_jll v0.3.26+2
  [83775a58] Zlib_jll v1.2.13+1
  [8e850b90] libblastrampoline_jll v5.8.0+1
  [8e850ede] nghttp2_jll v1.59.0+0
  [3f19e933] p7zip_jll v17.4.0+2
^C┌ Warning: Process I/O error
│   exception =
│    InterruptException:
│    Stacktrace:
│      [1] sigatomic_end
│        @ ./c.jl:146 [inlined]
│      [2] uv_write(s::Base.TTY, p::Ptr{UInt8}, n::UInt64)
│        @ Base ./stream.jl:1065
│      [3] unsafe_write(s::Base.TTY, p::Ptr{UInt8}, n::UInt64)
│        @ Base ./stream.jl:1141
│      [4] unsafe_write
│        @ ./io.jl:801 [inlined]
│      [5] unsafe_write(s::Base.TTY, p::Base.RefValue{UInt8}, n::Int64)
│        @ Base ./io.jl:799
│      [6] write
│        @ ./io.jl:805 [inlined]
│      [7] write(s::Base.TTY, b::UInt8)
│        @ Base ./stream.jl:1179
│      [8] write(io::Pkg.UnstableIO, b::UInt8)
│        @ Pkg ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Pkg.jl:46
│      [9] unsafe_write
│        @ ./io.jl:318 [inlined]
│     [10] unsafe_write
│        @ ./io.jl:801 [inlined]
│     [11] write
│        @ ./io.jl:835 [inlined]
│     [12] write(to::Pkg.UnstableIO, from::Base.PipeEndpoint)
│        @ Base ./io.jl:883
│     [13] (::Base.var"#879#880"{Base.PipeEndpoint, Pkg.UnstableIO, Base.PipeEndpoint})()
│        @ Base ./process.jl:313
└ @ Base process.jl:315
ERROR: TaskFailedException
Stacktrace:
  [1] wait(t::Task)
    @ Base ./task.jl:363
  [2] wait(x::Base.Process, syncd::Bool)
    @ Base ./process.jl:705
  [3] wait(x::Base.Process)
    @ Base ./process.jl:687
  [4] subprocess_handler(cmd::Cmd, ctx::Pkg.Types.Context, sandbox_ctx::Pkg.Types.Context, error_msg::String)
    @ Pkg.Operations ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:2077
  [5] (::Pkg.Operations.var"#132#136"{Bool, Cmd, Cmd, Nothing, Pkg.Types.Context, Vector{Tuple{String, Base.Process}}, String, Pkg.Types.PackageSpec})()
    @ Pkg.Operations ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:2008
  [6] withenv(::Pkg.Operations.var"#132#136"{Bool, Cmd, Cmd, Nothing, Pkg.Types.Context, Vector{Tuple{String, Base.Process}}, String, Pkg.Types.PackageSpec}, ::Pair{String, String}, ::Vararg{Pair{String}})
    @ Base ./env.jl:265
  [7] (::Pkg.Operations.var"#119#124"{String, Bool, Bool, Bool, Pkg.Operations.var"#132#136"{Bool, Cmd, Cmd, Nothing, Pkg.Types.Context, Vector{Tuple{String, Base.Process}}, String, Pkg.Types.PackageSpec}, Pkg.Types.PackageSpec})()
    @ Pkg.Operations ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1869
  [8] with_temp_env(fn::Pkg.Operations.var"#119#124"{String, Bool, Bool, Bool, Pkg.Operations.var"#132#136"{Bool, Cmd, Cmd, Nothing, Pkg.Types.Context, Vector{Tuple{String, Base.Process}}, String, Pkg.Types.PackageSpec}, Pkg.Types.PackageSpec}, temp_env::String)
    @ Pkg.Operations ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1741
  [9] (::Pkg.Operations.var"#117#122"{Dict{String, Any}, Bool, Bool, Bool, Pkg.Operations.var"#132#136"{Bool, Cmd, Cmd, Nothing, Pkg.Types.Context, Vector{Tuple{String, Base.Process}}, String, Pkg.Types.PackageSpec}, Pkg.Types.Context, Pkg.Types.PackageSpec, String, String})(tmp::String)
    @ Pkg.Operations ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1839
 [10] mktempdir(fn::Pkg.Operations.var"#117#122"{Dict{String, Any}, Bool, Bool, Bool, Pkg.Operations.var"#132#136"{Bool, Cmd, Cmd, Nothing, Pkg.Types.Context, Vector{Tuple{String, Base.Process}}, String, Pkg.Types.PackageSpec}, Pkg.Types.Context, Pkg.Types.PackageSpec, String, String}, parent::String; prefix::String)
    @ Base.Filesystem ./file.jl:819
 [11] mktempdir(fn::Function, parent::String)
    @ Base.Filesystem ./file.jl:815
 [12] mktempdir
    @ ./file.jl:815 [inlined]
 [13] #sandbox#116
    @ ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1787 [inlined]
 [14] test(ctx::Pkg.Types.Context, pkgs::Vector{Pkg.Types.PackageSpec}; coverage::Bool, julia_args::Cmd, test_args::Cmd, test_fn::Nothing, force_latest_compatible_version::Bool, allow_earlier_backwards_compatible_versions::Bool, allow_reresolve::Bool)
    @ Pkg.Operations ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:2000
 [15] test
    @ ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Operations.jl:1944 [inlined]
 [16] test(ctx::Pkg.Types.Context, pkgs::Vector{Pkg.Types.PackageSpec}; coverage::Bool, test_fn::Nothing, julia_args::Cmd, test_args::Cmd, force_latest_compatible_version::Bool, allow_earlier_backwards_compatible_versions::Bool, allow_reresolve::Bool, kwargs::@Kwargs{io::Pkg.UnstableIO})
    @ Pkg.API ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/API.jl:443
 [17] test(pkgs::Vector{Pkg.Types.PackageSpec}; io::Pkg.UnstableIO, kwargs::@Kwargs{})
    @ Pkg.API ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/API.jl:158
 [18] test(pkgs::Vector{Pkg.Types.PackageSpec})
    @ Pkg.API ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/API.jl:147
 [19] do_cmd(command::Pkg.REPLMode.Command, io::Base.TTY)
    @ Pkg.REPLMode ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/REPLMode/REPLMode.jl:407
 [20] do_cmds(commands::Vector{Pkg.REPLMode.Command}, io::Base.TTY)
    @ Pkg.REPLMode ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/REPLMode/REPLMode.jl:393
 [21] do_cmds(repl::REPL.LineEditREPL, commands::String)
    @ REPLExt ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/ext/REPLExt/REPLExt.jl:92
 [22] (::REPLExt.var"#31#34"{REPL.LineEditREPL, REPL.LineEdit.Prompt})(s::REPL.LineEdit.MIState, buf::IOBuffer, ok::Bool)
    @ REPLExt ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/ext/REPLExt/REPLExt.jl:122
 [23] #invokelatest#2
    @ ./essentials.jl:1030 [inlined]
 [24] invokelatest
    @ ./essentials.jl:1027 [inlined]
 [25] run_interface(terminal::REPL.Terminals.TextTerminal, m::REPL.LineEdit.ModalInterface, s::REPL.LineEdit.MIState)
    @ REPL.LineEdit ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/REPL/src/LineEdit.jl:2745
 [26] run_frontend(repl::REPL.LineEditREPL, backend::REPL.REPLBackendRef)
    @ REPL ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/REPL/src/REPL.jl:1408
 [27] (::REPL.var"#75#81"{REPL.LineEditREPL, REPL.REPLBackendRef})()
    @ REPL ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/REPL/src/REPL.jl:458

    nested task error: InterruptException:
    Stacktrace:
      [1] sigatomic_end
        @ ./c.jl:146 [inlined]
      [2] uv_write(s::Base.TTY, p::Ptr{UInt8}, n::UInt64)
        @ Base ./stream.jl:1065
      [3] unsafe_write(s::Base.TTY, p::Ptr{UInt8}, n::UInt64)
        @ Base ./stream.jl:1141
      [4] unsafe_write
        @ ./io.jl:801 [inlined]
      [5] unsafe_write(s::Base.TTY, p::Base.RefValue{UInt8}, n::Int64)
        @ Base ./io.jl:799
      [6] write
        @ ./io.jl:805 [inlined]
      [7] write(s::Base.TTY, b::UInt8)
        @ Base ./stream.jl:1179
      [8] write(io::Pkg.UnstableIO, b::UInt8)
        @ Pkg ~/.julia/juliaup/julia-nightly/share/julia/stdlib/v1.12/Pkg/src/Pkg.jl:46
      [9] unsafe_write
        @ ./io.jl:318 [inlined]
     [10] unsafe_write
        @ ./io.jl:801 [inlined]
     [11] write
        @ ./io.jl:835 [inlined]
     [12] write(to::Pkg.UnstableIO, from::Base.PipeEndpoint)
        @ Base ./io.jl:883
     [13] (::Base.var"#879#880"{Base.PipeEndpoint, Pkg.UnstableIO, Base.PipeEndpoint})()
        @ Base ./process.jl:313

IanButterworth · 2024-02-24T02:28:40Z

Seems we can't just not propagate --sysimage-native-code=no through julia_cmd? #42185

IanButterworth · 2024-02-24T02:37:25Z

But we are propagating the coverage/alloc tracking option.. so we should be able to and let the subprocess figure out where native code should be allowed, like the parent process did?

vtjnash · 2024-02-24T03:15:39Z

Yes, we could instead set this as an internal flag rather than changing jl_options so that it doesn't propagate

Seelengrab · 2024-02-24T06:40:48Z

That said, some packages spawn a lot of subprocesses, and this probably could affect those

I don't spawn any subprocesses in my CI, but I still see the regression going from 923fe2d74d4 to ea1a0d2512b. The former had ~2m runtime on nightly, while the latter is 7m.

Note that both runs are the exact same commit, just on a different branch since I rebased inbetween the two runs. The actual tests go from ~1m to ~6m.

923fe2d74d4:

ea1a0d2512b:

vchuravy · 2024-02-24T18:04:30Z

One issue is likely that a common test pattern is
:

using LLVM
using Test
# using all other test dependencies

And that after using LLVM we no longer use subsequent native code. If LLVM were loaded last all the cache files would be usable.

The crux is that this is a correctness fix and we have observed crashes without it. We definitely shouldn't propagate the taint to launched processes, but currently we don't track enough information to continue loading native code caches without the risk of crashing after skipping on native cache for code coverage purposes.

At worst the time is back to what it was before #52123 (slightly less since we don't need to regenerate files unnecessarily anymore)

Seelengrab · 2024-02-24T18:21:24Z

Does this also apply for anything other than LLVM? My package doesn't use it; is there a new guidance that I should do

# using of all other test dependencies

using MyPkg

# the actual test code

now? Seems a bit odd, especially if there's substantial overlap between the dependency chains. For my particular example, the only addition for test-only dependencies is Aqua.jl and Statistics (though I guess I can do without it).

The package in question is (soon-to-be-registered) Supposition.jl.

KristofferC · 2024-02-24T18:40:23Z

The crux is that this is a correctness fix and we have observed crashes without it.

Okay, but that still has to be weighed against the impact of this change. It's not reasonable to regress testing time by many x to fix a bug that has barely been seen in the ecosystem (only crash is CI with rr runner?).

When we use options like code coverage, we can't use the native code present in the cache file since it is not instrumented. PR #52123 introduced the capability of skipping the native code during loading, but created the issue that subsequent packages could have an explicit or implicit dependency on the native code. PR #53439 tainted the current process by setting `use_sysimage_native_code`, but this flag is propagated to subprocesses and lead to a regression in test time. Move this to a process local flag to avoid the regression. In the future we might be able to change the calling convention for cross-image calls to `invoke(ci::CodeInstance, args...)` instead of `ci.fptr(args...)` to handle native code not being present.

vchuravy · 2024-02-24T19:29:54Z

Okay, but that still has to be weighed against the impact of this change.

We could argue about correctness vs performance or we could simply fix it
see #53457

Does this also apply for anything other than LLVM

LLVM was just an example here.

there's substantial overlap between the dependency chains.

The dependency chain of MyPkg is being loaded with native code being abled, whence MyPkg is loaded (and code-coverage for it is enabled) we disabled native code.

I think there is a better long-term fix, but not one that will make it in time for 1.11 and doesn't carry a larger risk with it.

LilithHafner · 2024-02-24T20:00:40Z

At worst the time is back to what it was before #52123 (slightly less since we don't need to regenerate files unnecessarily anymore)

Nightly is currently significantly slower than 1.0, 1.6, and 1.10. I don't recall that being the case any time recently, so this is a regression of grater magnitude than any improvements in #52123

vchuravy · 2024-02-24T20:51:25Z

@LilithHafner my comment was with respect to @Seelengrab observation. The slowdowns you are seeing should be fixed by #53457 if they are not we need to do a deeper root-cause analysis.

When we use options like code coverage, we can't use the native code present in the cache file since it is not instrumented. PR #52123 introduced the capability of skipping the native code during loading, but created the issue that subsequent packages could have an explicit or implicit dependency on the native code. PR #53439 tainted the current process by setting `use_sysimage_native_code`, but this flag is propagated to subprocesses and lead to a regression in test time. Move this to a process local flag to avoid the regression. In the future we might be able to change the calling convention for cross-image calls to `invoke(ci::CodeInstance, args...)` instead of `ci.fptr(args...)` to handle native code not being present. --------- Co-authored-by: Jameson Nash <vtjnash@gmail.com>

This should fix the assertion failure that has been plaguing the Pkg tests, as discussed in #52123 (comment) (cherry picked from commit 6cbed31)

KristofferC · 2024-02-26T09:03:00Z

I'm removing this from backports since even though it is more correct it is causing unexpected effects. Can be added back when everything is resolved.

Seelengrab · 2024-02-26T09:12:56Z

It's resolved from my end with #53457, which even improved overall CI time by 25%! Thank you very much for the quick turnaround on this!

This should fix the assertion failure that has been plaguing the Pkg tests, as discussed in #52123 (comment) (cherry picked from commit 6cbed31)

When we use options like code coverage, we can't use the native code present in the cache file since it is not instrumented. PR #52123 introduced the capability of skipping the native code during loading, but created the issue that subsequent packages could have an explicit or implicit dependency on the native code. PR #53439 tainted the current process by setting `use_sysimage_native_code`, but this flag is propagated to subprocesses and lead to a regression in test time. Move this to a process local flag to avoid the regression. In the future we might be able to change the calling convention for cross-image calls to `invoke(ci::CodeInstance, args...)` instead of `ci.fptr(args...)` to handle native code not being present. --------- Co-authored-by: Jameson Nash <vtjnash@gmail.com> (cherry picked from commit b8a0a39)

KristofferC · 2024-02-26T09:17:51Z

Ok, thanks for checking, let's add those to then.

Backported PRs: - [x] #53205  - [x] #53170  - [x] #53228  - [x] #51361  - [x] #50480  - [x] #53301  - [x] #53354  - [x] #53388  - [x] #53429  - [x] #53437  Need manual backport: - [ ] #52505  - [ ] #53373  - [ ] #53439  Contains multiple commits, manual intervention needed: - [ ] #52913  - [ ] #53218  Non-merged PRs with backport label: - [ ] #53424  - [ ] #53125  - [ ] #52694  - [ ] #51479

…#53439) This should fix the assertion failure that has been plaguing the Pkg tests, as discussed in JuliaLang#52123 (comment)

When we use options like code coverage, we can't use the native code present in the cache file since it is not instrumented. PR JuliaLang#52123 introduced the capability of skipping the native code during loading, but created the issue that subsequent packages could have an explicit or implicit dependency on the native code. PR JuliaLang#53439 tainted the current process by setting `use_sysimage_native_code`, but this flag is propagated to subprocesses and lead to a regression in test time. Move this to a process local flag to avoid the regression. In the future we might be able to change the calling convention for cross-image calls to `invoke(ci::CodeInstance, args...)` instead of `ci.fptr(args...)` to handle native code not being present. --------- Co-authored-by: Jameson Nash <vtjnash@gmail.com>

…#53439) This should fix the assertion failure that has been plaguing the Pkg tests, as discussed in JuliaLang#52123 (comment)

When we use options like code coverage, we can't use the native code present in the cache file since it is not instrumented. PR JuliaLang#52123 introduced the capability of skipping the native code during loading, but created the issue that subsequent packages could have an explicit or implicit dependency on the native code. PR JuliaLang#53439 tainted the current process by setting `use_sysimage_native_code`, but this flag is propagated to subprocesses and lead to a regression in test time. Move this to a process local flag to avoid the regression. In the future we might be able to change the calling convention for cross-image calls to `invoke(ci::CodeInstance, args...)` instead of `ci.fptr(args...)` to handle native code not being present. --------- Co-authored-by: Jameson Nash <vtjnash@gmail.com>

staticdata: fix assert from partially disabled native code

42f84e4

vtjnash added backport 1.10 Change should be backported to the 1.10 release backport 1.11 Change should be backported to release-1.11 labels Feb 22, 2024

vtjnash requested review from vchuravy and IanButterworth February 22, 2024 18:51

vchuravy reviewed Feb 22, 2024

View reviewed changes

vchuravy approved these changes Feb 22, 2024

View reviewed changes

IanButterworth reviewed Feb 22, 2024

View reviewed changes

vtjnash merged commit 6cbed31 into master Feb 23, 2024
9 checks passed

vtjnash deleted the jn/52123-safe branch February 23, 2024 16:16

LilithHafner added performance Must go faster kind:regression Regression in behavior compared to a previous version labels Feb 24, 2024

LilithHafner added a commit that referenced this pull request Feb 24, 2024

Revert "staticdata: fix assert from partially disabled native code (#…

64d5166

…53439)" This reverts commit 6cbed31.

LilithHafner mentioned this pull request Feb 24, 2024

Revert "staticdata: fix assert from partially disabled native code" #53454

Closed

vchuravy mentioned this pull request Feb 24, 2024

Prevent tainting native code loading from propagating #53457

Merged

KristofferC mentioned this pull request Feb 26, 2024

Backports for 1.10.2 #53405

Merged

19 tasks

KristofferC removed backport 1.10 Change should be backported to the 1.10 release backport 1.11 Change should be backported to release-1.11 labels Feb 26, 2024

KristofferC added the backport 1.11 Change should be backported to release-1.11 label Feb 26, 2024

KristofferC mentioned this pull request Feb 26, 2024

Revert "do not start a new process for precompiling the test env" JuliaLang/Pkg.jl#3813

Closed

KristofferC removed the backport 1.11 Change should be backported to release-1.11 label Mar 1, 2024

LilithHafner mentioned this pull request Mar 8, 2024

Package CI performance regression #53657

Closed

IanButterworth mentioned this pull request Apr 16, 2024

2x regression in testing time of small package #53511

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

staticdata: fix assert from partially disabled native code #53439

staticdata: fix assert from partially disabled native code #53439

vtjnash commented Feb 22, 2024

vchuravy Feb 22, 2024

vchuravy left a comment

IanButterworth Feb 22, 2024

vchuravy Feb 22, 2024

LilithHafner commented Feb 23, 2024

IanButterworth commented Feb 24, 2024

LilithHafner commented Feb 24, 2024

vtjnash commented Feb 24, 2024

vtjnash commented Feb 24, 2024

LilithHafner commented Feb 24, 2024

IanButterworth commented Feb 24, 2024

IanButterworth commented Feb 24, 2024

vtjnash commented Feb 24, 2024

Seelengrab commented Feb 24, 2024

vchuravy commented Feb 24, 2024

Seelengrab commented Feb 24, 2024 •

edited

KristofferC commented Feb 24, 2024

vchuravy commented Feb 24, 2024

LilithHafner commented Feb 24, 2024

vchuravy commented Feb 24, 2024

KristofferC commented Feb 26, 2024

Seelengrab commented Feb 26, 2024

KristofferC commented Feb 26, 2024

		// The easiest way to do that is to disable it in all of them.
		jl_options.use_sysimage_native_code = JL_OPTIONS_USE_SYSIMAGE_NATIVE_CODE_NO;

staticdata: fix assert from partially disabled native code #53439

staticdata: fix assert from partially disabled native code #53439

Conversation

vtjnash commented Feb 22, 2024

vchuravy Feb 22, 2024

Choose a reason for hiding this comment

vchuravy left a comment

Choose a reason for hiding this comment

IanButterworth Feb 22, 2024

Choose a reason for hiding this comment

vchuravy Feb 22, 2024

Choose a reason for hiding this comment

LilithHafner commented Feb 23, 2024

IanButterworth commented Feb 24, 2024

LilithHafner commented Feb 24, 2024

vtjnash commented Feb 24, 2024

vtjnash commented Feb 24, 2024

LilithHafner commented Feb 24, 2024

IanButterworth commented Feb 24, 2024

IanButterworth commented Feb 24, 2024

vtjnash commented Feb 24, 2024

Seelengrab commented Feb 24, 2024

vchuravy commented Feb 24, 2024

Seelengrab commented Feb 24, 2024 • edited

KristofferC commented Feb 24, 2024

vchuravy commented Feb 24, 2024

LilithHafner commented Feb 24, 2024

vchuravy commented Feb 24, 2024

KristofferC commented Feb 26, 2024

Seelengrab commented Feb 26, 2024

KristofferC commented Feb 26, 2024

Seelengrab commented Feb 24, 2024 •

edited