(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)

* fix #41489: inference of `+(::Rational, Rational)`

* implement review comments

(cherry picked from commit cf4e1c4)

(cherry picked from commit 6240d35)

(cherry picked from commit 7bc38a0)

…inters (#41492)

(cherry picked from commit c49153d)

(cherry picked from commit 97f817a)

(cherry picked from commit 22c52a1)

…commit statuses (#41543)

(cherry picked from commit ffc340c)

* 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)

(cherry picked from commit e3a06c4)

…ue of `tag_name` (#41549)

(cherry picked from commit a9232d6)

We had apparently misspelled this entitlement, not allowing `lldb` to attach to official macOS builds.

(cherry picked from commit ad6740b)

(cherry picked from commit d732903)

Co-authored-by: Jeff Bezanson <jeff.bezanson@gmail.com>
(cherry picked from commit 1c92e0d)

Busybox `xargs` doesn't support `-L` option, so building Julia fails on Alpine Linux for example

(cherry picked from commit da28c17)

…name` (#41571)

(cherry picked from commit 23dbf16)

Helps #41512

(cherry picked from commit 468b157)

)

(cherry picked from commit be443ac)

(cherry picked from commit 430e5e0)

…ide an existing tarball (unless the user provides the `--force-overwrite` command-line flag) (#41591)

Co-authored-by: Elliot Saba <staticfloat@gmail.com>

Co-authored-by: Elliot Saba <staticfloat@gmail.com>
(cherry picked from commit 3ac7c38)

…41610)

(cherry picked from commit e1aeb8a)

(cherry picked from commit 480ff81)
(cherry picked from commit dad0f15)

(cherry picked from commit 9564bfb)

* add default "auto" as option to --check-bounds

* add to NEWS

(cherry picked from commit 7d0f769)

fixes #41047

(cherry picked from commit e6aca89)

(cherry picked from commit a2f5fe5)

…38483)"

This reverts commit 9d3a7c4.

* Setup CI for ASAN

* Launch the `sanitizers.yml` unsigned pipeline

* Use a workspace directory in ./tmp

* Add some log group headers to make the logs easier to navigate

* Install `julia` binary inside sandbox

* Double timeout

* More descriptive message from sanitizer CI

* Fix the path to the binary

* Use addenv

* Apply suggestions from code review

Co-authored-by: Elliot Saba <staticfloat@gmail.com>

* Group ASAN related files under contrib/asan/

* Remove redundant JULIA_PRECOMPILE=1

Co-authored-by: Dilum Aluthge <dilum@aluthge.com>
Co-authored-by: Elliot Saba <staticfloat@gmail.com>
(cherry picked from commit 84934e6)

…% compilation time reports (#41286)

* ensure `@time`'s inner timing functions are compiled

(cherry picked from commit 0dbd3f7)

(cherry picked from commit 02807b2)

fixes #41134

(cherry picked from commit 2e08ccd)

(cherry picked from commit 6d58068)

…1622)

* while loop -> for loop in _simplify_include_frames (fixes #41566)

prevents the possibility of a bounds error when i = 0

(cherry picked from commit ed4f316)

…xperimental pipeline (#41606)

(cherry picked from commit c95448f)

(cherry picked from commit 8b15db7)

(cherry picked from commit e196b85)

Fixes #41655

(cherry picked from commit 9442f1b)

)

Fixes #41615

(cherry picked from commit b692c9b)

n.b. `n == a->nrows + dec`

Fixes JuliaData/DataFrames.jl#2819

(cherry picked from commit 2e06a01)

(cherry picked from commit b3a99c0)

(cherry picked from commit 61b6994)

… new (#41645)

We ship our own compiler support libraries to ensure a minimum level of
support for BB-built libraries, however certain distros provide very
bleeding-edge compilers.  This can be a problem if we download an
_older_ `libstdc++.so` and forcibly link against that when launching
Julia, as when Julia itself is built with the local `g++`, it may use
symbols that don't exist in the BB-sourced `libstdc++.so`.

To address this, we default to not using BB-sourced CSLs if the
`libstdc++.so` that the native compiler would use contains a symbol that
our BB-sourced CSLs do not have.  We use the monotonically-climbing
`GLIBCXX_3.4.XX` version symbols for this purpose; encoding the "next"
version number within `deps/csl.mk`, and triggering the BB-avoidance if
that version exists within the system-provided `libstdc++.so`.

(cherry picked from commit 27c0291)

Co-authored-by: Jameson Nash <vtjnash@gmail.com>
(cherry picked from commit 2c02de8)

…the non-root CHOWN tests (#41682)

Co-authored-by: Elliot Saba <staticfloat@gmail.com>

Co-authored-by: Elliot Saba <staticfloat@gmail.com>
(cherry picked from commit 114ee17)

)

Co-authored-by: Elliot Saba <staticfloat@gmail.com>
(cherry picked from commit c7097c5)

…cumentation, and reorganize/rename/move a bunch of configuration files (#41698)

(cherry picked from commit e6e79f7)

#41700)

(cherry picked from commit 343c2b1)

…stead of `signature` (#41706)

* CI (Buildkite): for the signed pipeline test, use `signature_file` instead of `signature`

* Base64-decode the signature before writing it to the signature file

(cherry picked from commit f7f46af)

(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)

(cherry picked from commit 5af1cf0)

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)

Allows creating these ranges for any type of integer lengths.

Also need to be careful about using additive identity instead of
multiplicative, and be even more consistent now about types in a
few places.

Fixes #41517

(cherry picked from commit 4f77aba)

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)

(cherry picked from commit 2fbeef8)

(cherry picked from commit b50bf04)

…41722)

Also reverts "fixup to pull request #38405 (#41641)"

Seems to be causing hanging in CI testing.

This reverts commit 5af1cf0 and this
reverts commit 5a16805, reversing
changes made to 02807b2.

(cherry picked from commit 66f9b55)

(cherry picked from commit 4c3829d)

…Range{<:Rational})` (#41479)

* Fix length(::AbstractUnitRange), faster length(::AbstractUnitRange{<:Rational})

(cherry picked from commit 1c951f7)

(cherry picked from commit 4720378)