-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 for Julia 1.3-RC3 #33221
Backports for Julia 1.3-RC3 #33221
Conversation
@nanosoldier |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @ararslan |
I'm getting this on PkgEval when building this:
anything that should be done about that? |
(cherry picked from commit 09ff912)
Fixes #33177 (cherry picked from commit 4c8f8fa)
* Dispatch more cases to BLAS.gemm! * Use α and β instead of alpha′ and beta′ (cherry picked from commit 51b3227)
…33228) This has the following advantages: * It allows our buildbots to pass in which code signing identity they want to use (rather than having the identity hash hardcoded in our build system) * It stops blindly attempting to codesign on random user's machines * It causes codesign failure to stop the build (cherry picked from commit 0760842)
412c961
to
adfae3c
Compare
I would like to selfishly request a Pkg bump to whatever the latest 1.3 branch is for Pkg, so that it contains JuliaLang/Pkg.jl@45be6f6, as that will be important for users of 1.3 |
It should be backported into JuliaLang/Pkg.jl#1361. That PR merged and then we bump the Pkg version to that commit on Julia master and then backport that commit when merged. |
I fixed the inference hang on TravelingSalesmanExact by typing a vector concretely: ericphanson/TravelingSalesmanExact.jl#7 (comment). |
That's weird but thanks for fixing! |
This provides a number of benefits: * Significantly reduces the amount of work in win-extras, which I've always thought was an annoying wart in our build system. * Provides a consistent 7z executable on all platforms, which can be picked up by Pkg/BinaryProvider for consistent unzipping/untarring/ungzipping on all platforms. Note that on Windows, 7z is a repackaged binary from sourceforge and is the "full" 7z, whereas on all other platforms it is a p7zip build of the standalone 7za executable with all relevant patches applied. There are some format capability differences, but for the important things it should be fine. (cherry picked from commit b6ddd87)
I preemptively pushed #33353 to get an up to date PkgEval run. |
PkgEval run didn't reveal anything interesting. With Pkg bumped, I believe we should be able to tag RC-3 which actually has a chance to promote to 1.3. |
Win32 seems borken: |
That's an expected error; it's a temporary workaround for building Julia 1.2-, which didn't ship with 7z. That's why it's allowed to fail and not bother anything. The real error is the signing error below, it looks like |
Should look at #33370 before tagging RC3. |
Should #32327 be included? It's on the other backports lists. |
@nanosoldier |
This should be good to go when CI + nanosoldier comes back ok. |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @ararslan |
Lame :/. Could one of the recent commits have caused that? |
CI looks okay now and skimming over the Nanosoldier regressions, they look like noise to me. |
Backports for Julia 1.3-RC3
Backports for Julia 1.3-RC3
Backports for Julia 1.3-RC3
Backported PRs:
nothing
#33216 - Remove out-of-date docs on printingnothing
$MACOS_CODESIGN_IDENTITY
is set #33228 - macOS codesigning: only attempt if$MACOS_CODESIGN_IDENTITY
is setType{T}
#33303 - fix StackOverflowError on Julia 1.2 when constructing aNamedTuple
with value typeType{T}
#33270; stack overflow in named tuple ctor withType{T}
Type{T}
#33303 - fix StackOverflowError on Julia 1.2 when constructing aNamedTuple
with value typeType{T}
#33270; stack overflow in named tuple ctor withType{T}
GMP
andMPFR
, to fix performance regressions"