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.6] backports for 0.6.0-rc2 #21878

Merged
merged 77 commits into from
May 18, 2017
Merged

Conversation

tkelman
Copy link
Contributor

@tkelman tkelman commented May 14, 2017

  • pkgeval
  • @nanosoldier runbenchmarks(ALL, vs = "@6bdb3950bdf64152") vs 0.6.0-rc1

DrKrar and others added 30 commits May 13, 2017 17:50
* clearing the meaning of comment

* correct back file name.

(cherry picked from commit 1571b62)
… closure (#21700)

* fix serialization of multiple global bindings to the same object in a closure
(cherry picked from commit 3930eef)
most notably in Core.Inference, this may cause the addition of bad edges and suboptimal results

(cherry picked from commit 49c1910)
ref #21690

inference: improve function call signatures

ensures that abstract_iteration gets better information,
and that specialization can compile these methods ahead-of-time

(cherry picked from commit 0250e4f)
(cherry picked from commit c4ed32e)
ref #21721
(cherry picked from commit 3cfb989)
ref #21706
(cherry picked from commit d106662)
ref #21716

clarify some quasi-ambiguous or unnecessary method signatures

Without the fix to issue #21710, these are likely sources of
ambiguities.

(cherry picked from commit 79605e8)
This was caused by incorrectly using a TypeVar as the value of a static
parameter in the case of a compiled specialization whose signature is
not a leaf type. In this case, one slot was specialized on `Function`,
but the slot with the static parameter had a leaf type.

(cherry picked from commit a581292)
ref #21729
(cherry picked from commit 14da9d3)
ref #21707
* Improve docstrings for norm, vecnorm, normalize and normalize!

Add equations defining the norms, reorganize the docstrings by argument type,
and mention what "normalizing" means.

* Remove docstring for the norm() function

(cherry picked from commit e257ef4)
(cherry picked from commit b1d0897)
ref #21702
fix #21763

(cherry picked from commit 57a8f0a)
ref #21765
(cherry picked from commit ff73d57)
ref #21699

Replace visually confusing asterisks

(cherry picked from commit c21e77a)
* Optimize remotecall pattern used in distributed loading
(cherry picked from commit 9694de7)
Avoid a library call into GMP.

(cherry picked from commit 05708f8)
ref #21231

speed-up prevpow2 & nextpow2 for BigInt

(cherry picked from commit 42fd2a7)

GMP: add flipsign[!] functions and use more iszero/isneg/ispos

(cherry picked from commit f63bdfd)

add ZERO & ONE global BigInt constants for optimization

(cherry picked from commit b521acd)
… calls

(cherry picked from commit 66b8036)
ref #21718

don't insert toplevel expression unless there are imports

(cherry picked from commit 18291b0)

eliminate unnecessary array allocations from isexpr and extract_imports functions

(cherry picked from commit 305037a)

test fixes

(cherry picked from commit 24a74a5)
@GregPlowman
Copy link
Contributor

I guess it's too late for rc2, but would it be possible for PR #21695 to be included before 0.6 final?
And also included in 0.5.3?

@tkelman
Copy link
Contributor Author

tkelman commented May 17, 2017

d818788 was in pretty good shape on pkgeval https://gist.github.com/df43d5af59dd34a3520e59a57c7ff3d0 with one spurious new failure in LPVSpectral, and Feather is segfaulting on this branch as opposed to freezing on rc1 (it was working up until April 6th though https://github.com/JuliaCI/pkg.julialang.org/blob/88a41b735886f267c8e71ad63be5b3e7eba38449/logs/Feather_0.6.log)

But I think there have been enough new bugfixes on master that it'd be better to get them in here and re-run pkgeval again.

andreasnoack and others added 9 commits May 16, 2017 23:34
…1877 (#21889)

Make sure the methods are getting called from A'\b and A.'\b.

Don't promote Factorizations in general

Promote Bunch-Kaufman since it doesn't have a generic fallback solver
(cherry picked from commit 57ebd82)
* Add NEWS.md entry for three-argument rem and the new rem2pi (#10946).

* Clarify precise behaviour

(cherry picked from commit 8f9a948)
Also test for `fd != -1` instead since that is a defined invalid value.

(cherry picked from commit 84eeb40)
ref #21893
This would widen e.g. `Complex{T} where T` to `_ <: Complex`, which
is valid in some sense but yields a type that's not a supertype of
the input, which is bad.

(cherry picked from commit f46ba0a)
ref #21907
@tkelman
Copy link
Contributor Author

tkelman commented May 17, 2017

@nanosoldier runbenchmarks(ALL, vs = "@6bdb3950bdf64152") vs 0.6.0-rc1

@tkelman
Copy link
Contributor Author

tkelman commented May 17, 2017

@jlbuild !nuke

Base.runtests()
Base.runtests("pkg libgit2-online download")

@jlbuild
Copy link

jlbuild commented May 17, 2017

Status of be004c1 builds:

Builder Name Nuke Build Download Code Output
linux32 COMPLETE COMPLETE Download ERRORED
linux64 COMPLETE COMPLETE Download COMPLETE
linuxaarch64 CANCELED N/A N/A N/A
linuxarmv7l COMPLETE ERRORED N/A N/A
linuxppc64le COMPLETE COMPLETE Download ERRORED
osx64 COMPLETE ERRORED N/A N/A
win32 CANCELED N/A N/A N/A
win64 ERRORED N/A N/A N/A

@nanosoldier
Copy link
Collaborator

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

@tkelman
Copy link
Contributor Author

tkelman commented May 17, 2017

ouch, what happened to date parsing?

@tkelman
Copy link
Contributor Author

tkelman commented May 17, 2017

hm. flaky false alarm then? @nanosoldier runbenchmarks(ALL, vs = "@6bdb3950bdf64152")

@nanosoldier
Copy link
Collaborator

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

@tkelman
Copy link
Contributor Author

tkelman commented May 18, 2017

https://gist.github.com/4804ae73c6d5cec89d78890617c558dc same Feather issue (#21920) and MatrixNetworks had a tolerance too tight

merging and tagging this as rc2

@tkelman tkelman merged commit 419992a into release-0.6 May 18, 2017
@tkelman tkelman deleted the tk/backports-0.6.0-rc2 branch May 18, 2017 02:29
@tkelman
Copy link
Contributor Author

tkelman commented May 18, 2017

@staticfloat @yuyichao can you check on and reconnect the old arm buildbot? the new buildbots aren't quite ready to be making releases off of just yet

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.