Skip to content
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

[release-0.5] backports for 0.5.0-rc3 #18156

Merged
merged 115 commits into from
Aug 22, 2016
Merged

Conversation

tkelman
Copy link
Contributor

@tkelman tkelman commented Aug 20, 2016

@nanosoldier runbenchmarks(ALL, vs = "@0350e5769b43f56c4c570741b0f5b2edf9399dc7") (vs rc2 tag)

will be running pkgeval here to check for any regressions

tkelman and others added 30 commits August 19, 2016 23:17
This mostly reverts #17906 and puts #15521 back in place,
but from a slightly more permanent download location now.

Unfortunately using the latest opensuse copy of the gcc dll's
is causing issues when a cygwin-built Julia tries to load an
opensuse-built libzmq.dll. Using these slightly old gcc 5 versions
seems to fix it. I suspect the difference is which libstdc++ ABI
is being used. GCC 5 has both old and new available, but many distros
had it using the old ABI by default for compatibility. GCC 6 (which
opensuse is using now) is more likely to be using the new ABI by
default.

(cherry picked from commit 477a026)
ref #18059
some of the spawn and cmdlineargs tests may fail in a no-GPL
Windows build if executed outside of the build environment
(all of which are GPL themselves...), we could either skip them
or try to get them to work via calling powershell or some other
non-GPL coreutils replacement (toybox? uutils? sbase + now-LPGL cygwin?)

(cherry picked from commit 2a9dd3b)
ref #17851
(cherry picked from commit a434002)
ref #17783
The curl build depends on mbedtls and libssh2
Patch for mbedtls to allow curl to build with mbedtls support
Add curl to LICENSE.md, README.md and all the other various locations

(cherry picked from commit 046c6eb)
ref #17783
Enforce curl as a dependency for the libgit2 build.
Fix the libgit2 clean target
Build curl only on linux and osx.
Add pkg-config to build dependencies in README.md. Required to detect curl in libgit2 build.

(cherry picked from commit 3687527)
ref #17783
(cherry picked from commit 6fd91b2)
ref #17929
also fix some code formatting

(cherry picked from commit 28d8b80)
ref #17973
Vararg is only exact if in covariant position

also make getfield_tfunc monotonic for the case where the type has one
field, to avoid the same bug

fix #16530

(cherry picked from commit aeaff55)
ref #17953
  * Replace a malformed link in `write` docstring with a literal `write` rather than
    a real cross-reference, since that would just cross-reference itself. Also move
    `write` docstring inline.

  * Remove cross-reference for `<<` from inside a literal since text inside a literal
    can't contain a link. A cross-reference to `<<` already appears at the end of the
    docstring.

(cherry picked from commit 2301c27)
ref #17969
It turns out we were returning a Vector{Int} for operations that should return a Range

(cherry picked from commit 3bb7815)
ref #17980
(cherry picked from commit e4b5233)
fixes #17938
* fix a typo in Base.split

* fixup! fix a typo in Base.split

(cherry picked from commit 75e88af)
(cherry picked from commit bb7272e)
ref #18012
Fixes #17819. Also document not being allowed to call back into Julia.

(cherry picked from commit aea8180)
ref #18016
This fixes a performance regression in the lucompletepiv benchmark triggered by generalizing _array_for to work with indices. This call, first introduced in b363cc7, likely always triggered dynamic method dispatch. The generalization to indices seemed to make that worse.

(cherry picked from commit cb623f8)
ref #18009
(cherry picked from commit 1d49ec0)
@tkelman
Copy link
Contributor Author

tkelman commented Aug 22, 2016

@nanosoldier runbenchmarks(ALL, vs = "@0350e5769b43f56c4c570741b0f5b2edf9399dc7") (merge commit at fd14be9 vs rc2 tag)

(now obsolete)

@timholy
Copy link
Sponsor Member

timholy commented Aug 22, 2016

Instead of reverting the DFT change, can you cherry pick #18178?

JeffBezanson and others added 2 commits August 22, 2016 05:55
This should help #17932. If a function returns an unanticipated type
that wasn't part of the `Union` seen by inference, do dynamic
dispatch instead of erroring.

(cherry picked from commit b0cf591)
ref #18046
(cherry picked from commit e4ea3a7)
ref #18178
@tkelman
Copy link
Contributor Author

tkelman commented Aug 22, 2016

@nanosoldier runbenchmarks(ALL, vs = "@0350e5769b43f56c4c570741b0f5b2edf9399dc7") (merge commit at 2406ed9 vs rc2 tag)

@tkelman
Copy link
Contributor Author

tkelman commented Aug 22, 2016

I'm running PkgEval again at 2406ed9, with only #18130 reverted and fixes cherry-picked from #18046 and #18178.

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels

@lruthotto
Copy link

As for KrylovMethods: I could not reproduce the issue on my machine and I've changed the test. Previously the direction was chosen randomly (which caused the test to fail sometimes). Now, it is fixed and should always work.

@tkelman
Copy link
Contributor Author

tkelman commented Aug 22, 2016

@nanosoldier runbenchmarks(ALL, vs = "@0350e5769b43f56c4c570741b0f5b2edf9399dc7") (merge commit at e5b8332 vs rc2 tag)

@JeffBezanson are you going to merge #18046 ?

@JeffBezanson
Copy link
Sponsor Member

Merged.

@tkelman
Copy link
Contributor Author

tkelman commented Aug 22, 2016

At 2406ed9 we only had the known exception type change with BandedMatrices, and a tolerances-too-tight random failure in PolynomialRoots: https://gist.github.com/08599e229e722ec059f90a17ea5259fc

I'm hoping that #18183 won't have any unintended consequences.

@tkelman tkelman merged commit 37334d9 into release-0.5 Aug 22, 2016
@tkelman tkelman deleted the tk/backports-0.5.0-rc3 branch August 22, 2016 22:02
@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels

@ufechner7
Copy link

Is there an explanation for the performance degration in the BitArray tests?

@KristofferC
Copy link
Sponsor Member

Probably #18046?

@tlnagy
Copy link
Contributor

tlnagy commented Aug 23, 2016

@tkelman I see that #18122 is in the backports list? Gadfly's doctests are still failing with the same InexactError on RC3.

@tkelman
Copy link
Contributor Author

tkelman commented Aug 23, 2016

ca5c823 it's in there

@tlnagy
Copy link
Contributor

tlnagy commented Aug 23, 2016

Seems like it didn't completely fix the problem then (using Gadfly master) because:

julia> using RDatasets

julia> using Gadfly

julia> plot(dataset("ggplot2", "diamonds"), x="Price", color="Cut",
            Geom.histogram(bincount=30, density=true))
Error showing value of type Gadfly.Plot:
ERROR: InexactError()
 in copy!(::Base.LinearFast, ::Array{Int64,1}, ::Base.LinearFast, ::Array{Float64,1}) at ./abstractarray.jl:559
 in broadcast!(::Base.#identity, ::Array{Int64,1}, ::Array{Float64,1}) at ./broadcast.jl:24
 in apply_statistic(::Gadfly.Stat.HistogramStatistic, ::Dict{Symbol,Gadfly.ScaleElement}, ::Gadfly.Coord.Cartesian, ::Gadfly.Aesthetics) at /Users/tamasnagy/.julia/v0.5/Gadfly/src/statistics.jl:330
 in apply_statistics(::Array{Gadfly.StatisticElement,1}, ::Dict{Symbol,Gadfly.ScaleElement}, ::Gadfly.Coord.Cartesian, ::Gadfly.Aesthetics) at /Users/tamasnagy/.julia/v0.5/Gadfly/src/statistics.jl:38
 in render_prepare(::Gadfly.Plot) at /Users/tamasnagy/.julia/v0.5/Gadfly/src/Gadfly.jl:740
 in render(::Gadfly.Plot) at /Users/tamasnagy/.julia/v0.5/Gadfly/src/Gadfly.jl:799
 in display(::Base.REPL.REPLDisplay{Base.REPL.LineEditREPL}, ::MIME{Symbol("text/html")}, ::Gadfly.Plot) at /Users/tamasnagy/.julia/v0.5/Gadfly/src/Gadfly.jl:1062
 in macro expansion at ./multimedia.jl:143 [inlined]
 in display(::Gadfly.Plot) at /Users/tamasnagy/.julia/v0.5/Gadfly/src/Gadfly.jl:1014
 in print_response(::Base.Terminals.TTYTerminal, ::Any, ::Void, ::Bool, ::Bool, ::Void) at ./REPL.jl:154
 in print_response(::Base.REPL.LineEditREPL, ::Any, ::Void, ::Bool, ::Bool) at ./REPL.jl:139
 in (::Base.REPL.##22#23{Bool,Base.REPL.##33#42{Base.REPL.LineEditREPL,Base.REPL.REPLHistoryProvider},Base.REPL.LineEditREPL,Base.LineEdit.Prompt})(::Base.LineEdit.MIState, ::Base.AbstractIOBuffer{Array{UInt8,1}}, ::Bool) at ./REPL.jl:652
 in run_interface(::Base.Terminals.TTYTerminal, ::Base.LineEdit.ModalInterface) at ./LineEdit.jl:1579
 in run_interface(::Base.Terminals.TTYTerminal, ::Base.LineEdit.ModalInterface) at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?
 in run_frontend(::Base.REPL.LineEditREPL, ::Base.REPL.REPLBackendRef) at ./REPL.jl:903
 in run_repl(::Base.REPL.LineEditREPL, ::Base.##930#931) at ./REPL.jl:188
 in _start() at ./client.jl:360
 in _start() at /Applications/Julia-0.5.app/Contents/Resources/julia/lib/julia/sys.dylib:?

julia> versioninfo()
Julia Version 0.5.0-rc3+0
Commit e6f843b (2016-08-22 23:43 UTC)
Platform Info:
  System: Darwin (x86_64-apple-darwin13.4.0)
  CPU: Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell)
  LAPACK: libopenblas64_
  LIBM: libopenlibm
  LLVM: libLLVM-3.7.1 (ORCJIT, haswell)

@tkelman
Copy link
Contributor Author

tkelman commented Aug 23, 2016

How's master? Worth a new issue probably?

@tlnagy
Copy link
Contributor

tlnagy commented Aug 23, 2016

Testing right now. New issue here: GiovineItalia/Gadfly.jl#880. I'll open one against Base once we figure out what's wrong.

vchuravy pushed a commit to JuliaLang/LazyArtifacts.jl that referenced this pull request Oct 2, 2023
…0.5.0-rc3

[release-0.5] backports for 0.5.0-rc3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.