release-1.7: Backports for 1.7-RC1/1.7-beta4 #41499
Conversation
(cherry picked from commit 7409a1c)
(cherry picked from commit 4733c00)
ref #40562 (comment) (cherry picked from commit 10b010f)
Discovered while working on #40737. Currently, this throws an unintuitive error: ```julia julia> a, f()... = 1, 2, 3 ERROR: syntax: ssavalue with no def Stacktrace: [1] top-level scope @ REPL[1]:1 ``` Might as well fix this properly - Why not allow function definitions to slurp a little from time to time? ;) (cherry picked from commit 5c49a0d)
* Transition the `coverage-linux64` pipeline to Buildkite * Simplify, run inside of a sandbox * Upload coverage reports to Codecov and Coveralls * Add `COVERALLS_TOKEN` Co-authored-by: Elliot Saba <staticfloat@gmail.com> (cherry picked from commit 9d5f31e)
* Code coverage: fix the code coverage pipeline * Run all tests (cherry picked from commit 05e4138)
* Add "Check whitespace" buildkite job * Add `key` values for later `wait` blocks * Add "embedding tests" to buildkite configuration * Eliminate unnecessary work in buildkite builds Don't bother to precompile the Julia system image like we normally would want to if we're just going to run things once. Also use `JULIA_NUM_CORES` instead of hard-coding `-j 6` into the buildsystem. * Update embedding.yml * Update whitespace.yml (cherry picked from commit a2af845)
* Comment out signed pipeline test This is confirmed working, so let's comment it out until it's actually used by a codesigning step or similar. * Specifically notify llvm passes (cherry picked from commit f2d7300)
* Add `/cache/repos` as a mapping into the CI sandbox This should allow `git` to find its cached objects properly, which should silence the warnings on CI, and also give us the proper git version info within buildkite builds * Break up `llvmpasses` output a bit * Provide `/cache/repos` for `whitespace` as well * Give a positive message if whitespace check passes It's a little unnerving to have a silent command block in buildkite, so let's output a success message if everything is on the up-and-up (cherry picked from commit 460e981)
when building with USE_BINARYBUILDER=0 (cherry picked from commit 19ecf00)
(cherry picked from commit 8efdf85)
(cherry picked from commit 6240d35)
(cherry picked from commit 97f817a)
(cherry picked from commit 22c52a1)
* Add `less` to the `llvm-passes` rootfs image Also, sort the entries of `packages` in alphabetical order. * Update llvm-passes.jl (cherry picked from commit 516af1b)
We had apparently misspelled this entitlement, not allowing `lldb` to attach to official macOS builds. (cherry picked from commit ad6740b)
|
@nanosoldier |
|
@nanosoldier |
|
This error
indicates that libblastrampoline does not support Backporting #41530 would require backporting #41522 which updated libblastrampoline. Given the trouble we are experiencing with ASN on CI #41606, maybe it's better to not backport #41530, to avoid complicating the release process? |
(cherry picked from commit 5386fa6)
(cherry picked from commit 71308eb)
(cherry picked from commit 8fa8530)
Makes the worker struct threadsafe as well as flushing the GC messages (cherry picked from commit 0c073cc)
This seems to be a fairly arbitrary case for throwing exceptions, when the user might often use this value in arithmetic afterwards, which is not checked. It leads to awkward complexity in the API however, where it may be unclear which function to reach for, with no particular justification for why a particular usage is "safe". And it inhibits optimization and performance due to the additional checks and error cases (and is not even entirely type-stable). (cherry picked from commit 3eefaf0)
This is not a particularly meaningful combination (LLVM dislikes it). (cherry picked from commit f7fdcac)
(cherry picked from commit 8464101)
(cherry picked from commit 471e893)
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
|
@KristofferC @ararslan I just noticed beta4 was not released. I wonder if it is by oversight? https://github.com/JuliaLang/julia/releases |
|
We're waiting on being able to code sign Windows binaries again, Elliot is looking into it |
|
Ah, I see. Thanks for the clarification. |
Backported PRs:
coverage-linux64pipeline to Buildkite #41238partially_inline!withisdefined#40628Tuple{Union{}}#41483+(::Rational, Rational)#41491hvncat: Better handling of 0- and 1-length dims/shape args #41197summarysizeon arrays of inlined structs with pointers #41492llvm-passesrootfs image #41544.*with*in some 3-arg*methods #41545tag_name#41549get-task-allowentitlement #41559-Loption toxargswith-n#41583tag_name#41571_totuple#41515hvncat: Stronger argument checks #41196--force-overwritecommand-line flag) #41591hvncat: Ensure output ndims are >= the ndims of input arrays #41201upload_rootfs_imagefunction #41610@time's main timing block. Fixes >100% compilation time reports #41286sanitizersbuilders (e.g.asan) to the experimental pipeline #41606deleteat!#41646.buildkite/rootfs_imagesdirectory #41648USE_BINARYBUILDER_CSL=0when local CSL is new #41645fieldtype_tfuncfor union types #41667file.jltests to allow for bothEPERMandEINVALin the non-root CHOWN tests #41682package_linux64anddoctestbuilders #41541signature_fileinstead ofsignature#41706length(::OrdinalRange)for empty ranges of dimensionful numbers #41595length(::AbstractUnitRange)and speed uplength(::AbstractUnitRange{<:Rational})#41479Non-merged PRs with backport label:
jl_cumulative_compile_time_nsglobal (and reentrant). #41733package_linuxandtester_linuxfor more Linux architectures #41707usingthread-safe #41602UniformScaling#41325