julia 1.11.0-rc4

[cho-m]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

Potentially the final RC - https://github.com/JuliaLang/julia/milestone/46

[carlocab]

Test failure is

  [ Info: Writing test result data to /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/test
  ERROR: LoadError: SystemError: opening file "/opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/test/results_1.json": Operation not permitted

We should probably find a way to convince this to write inside testpath instead.

[cho-m]

Test failure is

  [ Info: Writing test result data to /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/test
  ERROR: LoadError: SystemError: opening file "/opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/test/results_1.json": Operation not permitted

We should probably find a way to convince this to write inside testpath instead.

Can probably try deleting CI variable https://github.com/JuliaLang/julia/blob/v1.11.0-rc4/test/runtests.jl#L431-L434

    if Base.get_bool_env("CI", false)
        @info "Writing test result data to $(@__DIR__)"
        write_testset_json_files(@__DIR__, o_ts)
    end

[cho-m]

After that fix, the next part of test failed. Not sure what it is trying with the curl library

  ==> /opt/homebrew/Cellar/julia/1.11.0-rc4/bin/julia --startup-file=no --history-file=no --project=/private/tmp/julia-test-20240930-63939-4x5a9o --procs 4 --eval using Pkg; Pkg.add("Example")
    Installing known registries into `~/.julia`
         Added `General` registry to ~/.julia/registries
      Updating registry at `~/.julia/registries/General.toml`
     Resolving package versions...
     Installed Example ─ v0.5.5
      Updating `~/Project.toml`
    [7876af07] + Example v0.5.5
      Updating `~/Manifest.toml`
    [7876af07] + Example v0.5.5
  Precompiling project...
      320.4 ms  ✓ Example
    1 dependency successfully precompiled in 0 seconds
  ┌ Error: curl_multi_assign: 1
  └ @ Downloads.Curl /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/stdlib/v1.11/Downloads/src/Curl/utils.jl:57
  ┌ Error: curl_multi_assign: 1
  └ @ Downloads.Curl /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/stdlib/v1.11/Downloads/src/Curl/utils.jl:57
  ┌ Error: curl_multi_assign: 1
  └ @ Downloads.Curl /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/stdlib/v1.11/Downloads/src/Curl/utils.jl:57
  
  [64007] signal 11 (2): Segmentation fault: 11
  in expression starting at none:0
  curl_multi_socket_action at /opt/homebrew/Cellar/curl/8.10.1/lib/libcurl.4.dylib (unknown line)
  curl_multi_socket_action at /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/stdlib/v1.11/Downloads/src/Curl/Curl.jl:51 [inlined]
  curl_multi_socket_action at /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/stdlib/v1.11/Downloads/src/Curl/Curl.jl:59 [inlined]
  macro expansion at /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/stdlib/v1.11/Downloads/src/Curl/utils.jl:56 [inlined]
  #55 at /opt/homebrew/Cellar/julia/1.11.0-rc4/share/julia/stdlib/v1.11/Downloads/src/Curl/Multi.jl:190

[carlocab]

Could just skip it, maybe, as long as Pkg.add below works.

[cho-m]

Bit worried about segfault.

---

Also, looks like release is soon - JuliaLang/julia#55953

[cho-m]

Looks like we did report an issue when bumping curl - JuliaLang/Downloads.jl#260

[cho-m]

Getting closer. ARM macOS passes. Intel macOS doesn't seem to be picking up bundled curl.

[cho-m]

Tried switching to smaller testcase which should have cut down time by ~1min:

    Overall     | 7353890       4  7353894  1m07.4s

vs

    Overall     | 1765       1   1766  12.5s

---

However, full test is still going beyond 5min limit.

The startup time of Base.runtests is slow so can skip that entirely like we were previously doing for Monterey. The alternative would be increasing test time in brew for intel runners.