-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Backports 1.6-rc1 #39160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backports 1.6-rc1 #39160
Conversation
* added automatic keyword assignment support to @test macro * added some tests for test macro using atol keyword * x = a.x syntax support added * Update stdlib/Test/src/Test.jl Co-authored-by: Simeon Schaub <[email protected]> Co-authored-by: Simeon Schaub <[email protected]> (cherry picked from commit 6c42190)
(cherry picked from commit f46da9e)
(cherry picked from commit 0949eb2)
Instead of writing out to actual `$HOME`, create a temporary directory and set that as `$HOME`/`$USERPROFILE`. (cherry picked from commit 7a6f423)
(cherry picked from commit fd671b3)
Sometimes we want to widen the compilation signature, but then end up with something which does not fit the original pattern. This then can cause problems later, when we try to use the Method (from the cache), but discover it does not actually match the call. Fixes #38999 (cherry picked from commit 8937f7e)
|
@nanosoldier |
|
@nanosoldier |
|
Something went wrong when running your job: Logs and partial data can be found here |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt |
…39226) Co-authored-by: Ian McInerney <[email protected]>
Co-authored-by: Dilum Aluthge <[email protected]>
(cherry picked from commit 2bbd5fb)
GCC 11 has changed header dependencies again, so the build of LLVM fails because <limits> wasn't being included when it should be. This is already fixed upstream in LLVM 12. (cherry picked from commit 4935775)
(cherry picked from commit 81701f1)
(cherry picked from commit 918ab6d)
(cherry picked from commit 6e9309d)
(cherry picked from commit 491d925)
(cherry picked from commit 7e85405)
mbedtls-cmake-findpy.patch lacks some whitespace that exists in the target file, which causes patch application failure when the patch tool is strict about whitespace. This teensy diff makes the patch's whitespace strictly match that in the target file. (cherry picked from commit 6416a3e)
(cherry picked from commit dbaca8b)
(cherry picked from commit debf26e)
(cherry picked from commit df2a1c5)
Co-authored-by: Julian Samaroo <[email protected]> (cherry picked from commit 0fe05cb)
If you had 2 aliases that both matched, we might print
```S{T} where T (alias for S{T} where T)```
which is clearly unnecessary.
(cherry picked from commit 48ad01d)
(cherry picked from commit b6df6c2)
Always a bit more compact in this form, and somewhat easier to implement too (thus keeping this consistent with the corrected typealias printing). (cherry picked from commit ee816ef)
(cherry picked from commit 80ace52)
(cherry picked from commit 8631089)
With constant-propagation, inference (and Varargs runtime) is likely better able to handle this version now (and it removes the n^2 behavior definitions for semi-low argument counts). Now we also need to force Vararg specialization up to 16 arguments manually, so we do that explicitly (and slightly hack-y). Fixes regression in #39175 (cherry picked from commit 5cd1e3e)
Co-authored-by: Dilum Aluthge <[email protected]> (cherry picked from commit f0e8ee6)
This was inserting a method with signature [Int, Int], rather than
Tuple{typeof(+), Int, Int}. Fix that and add a test for it so it doesn't
happen again.
(cherry picked from commit b9f8b8b)
|
@nanosoldier |
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt |
|
@fingolfin The incoming CBindingGen v0.4.5 release supports LLVM 11.0.1, so this should resolve the CBindingGen, P4est, and PLCTag package tests. |
|
I ran the benchmarks locally and didn't see anything completely crazy. There are some things that might be real regressions but with the server situation being what it is I think we have to go on with RC1 and then perhaps we can do a proper check for RC2. |
show_sym#38830 - fix erroneous code path withinshow_symjl_n_threads#38938 - Fix symbol trampolines for OSX and exportjl_n_threadsp7zip_jllenvironment setup #39155 - Fixp7zip_jllenvironment setupjl_uncompress_argnames#39215 - fix return type forjl_uncompress_argnamesusing Pkg.Artifactswith LazyArtifacts #39210 - [Artifacts]: Supportusing Pkg.Artifactswith LazyArtifactsunioninvalidation #39251 - Fix binaryplatformsunioninvalidationMain.ARGSunresolved on startup #39262 - fix Can't shadow ARGS in Main #39259, leaveMain.ARGSunresolved on startupT[elements...]#39252 - Prevent TOML invalidation by pirates ofT[elements...]Tincat_similar#39292 - Force-specialize onTincat_similarextremawith dims inferrable #39321 - makeextremawith dims inferrableenable_finalizerstest #39336 - fix failingenable_finalizerstestwidenconst_bestguesscall #38871 - rm unnecessarywidenconst_bestguesscallNeed manual backport:
Non-merged PRs with backport label:
..function #39446 - fix Regression for@which 1..2#39426, at-which not working with..functionWorkerstruct thread-safe. #38405 - Make Distributed.jlWorkerstruct thread-safe.