PyPy 5.4 release beginning
Hi. I would like to release PyPy2 v5.4. There is one failing test on linux64 which has to do with test_setrlimit() on bencher4. Are there any other release blockers? Branches to be merged? Matti
Hi Matti, On 24 August 2016 at 10:44, Matti Picus <matti.picus@gmail.com> wrote:
Hi. I would like to release PyPy2 v5.4. There is one failing test on linux64 which has to do with test_setrlimit() on bencher4.
Did you mean on the OS/X 64 buildslave? Should be fixed in 6bfe423a36a4.
Are there any other release blockers? Branches to be merged?
There are a few branches around but I think that they are not ready to be merged to default, as far as I can tell. Armin
On 24/08/16 20:16, Armin Rigo wrote:
I meant this one, failing for a few days now http://buildbot.pypy.org/summary/longrepr?testname=&builder=pypy-c-jit-linux-x86-64&build=3709&mod=module%2Ftest_lib_pypy as can be seem on the summary for linux-x86-64 on default http://buildbot.pypy.org/summary?builder=pypy-c-jit-linux-x86-64&branch=default I tracked this down to the test_setrlimit() test in test_lib_pypy/test_resources.py, skipping that test removes the SIGKILL failure Matti
Hi Matti, On 24 August 2016 at 14:08, Matti Picus <matti.picus@gmail.com> wrote:
Ah. As it turns out, the fix I did for OS/X applies here too. It should work from the next run, hopefully. (It got a crash because it called set_rlimit() with (0, 0), which instantly killed the process because it was using more than 0 seconds of CPU.) A bientôt, Armin.
The builds are ready and buildbots green (enough IMO). http://buildbot.pypy.org/nightly/release-5.x, any of the 86635-77392ad26350 binaries should be good to go. Please download and test them, especially the OSX and ARM ones. Anyone who is proficient with scipy/pandas/matplotlib could try their test suites out, upstream numpy should install on all platforms although there are known shortcomings with new buffer interface compatibility. I will be unable to repackage and upload to bitbucket for the next few days, so if anyone with fast internet can run the repackages script it would be very helpful: - update your pypy repo on linux - create a tmp directory anywhere in the repo - run pypy/tools/release/repackage.sh - upload the resulting 10 binary packages (8 precompiled, 2 source) to bitbucket/pypy/pypy/downloads - update pypy.org/downloads with the hashes printed out at the end of the script, or post them here We do not have ppc builds, so those would be helpful too. Thanks, and thanks to the team for pushing PyPy forward! Matti
Hi Matti, On 29 August 2016 at 01:14, Matti Picus <matti.picus@gmail.com> wrote:
Thanks for the work! The hg tag you created: "Added tag release-pypy2.7-v5.4.0 for changeset 68bb3510d821", is a changeset from default. Is that expected? Didn't you mean to use 77392ad26350?
We do not have ppc builds, so those would be helpful too.
I'm building them now. A bientôt, Armin.
On 30/08/16 19:10, Armin Rigo wrote:
https://bitbucket.org/pypy/pypy/downloads. If no-one complains in the next day or so I will finish the release. Matti
Hi Matti, On 24 August 2016 at 10:44, Matti Picus <matti.picus@gmail.com> wrote:
Hi. I would like to release PyPy2 v5.4. There is one failing test on linux64 which has to do with test_setrlimit() on bencher4.
Did you mean on the OS/X 64 buildslave? Should be fixed in 6bfe423a36a4.
Are there any other release blockers? Branches to be merged?
There are a few branches around but I think that they are not ready to be merged to default, as far as I can tell. Armin
On 24/08/16 20:16, Armin Rigo wrote:
I meant this one, failing for a few days now http://buildbot.pypy.org/summary/longrepr?testname=&builder=pypy-c-jit-linux-x86-64&build=3709&mod=module%2Ftest_lib_pypy as can be seem on the summary for linux-x86-64 on default http://buildbot.pypy.org/summary?builder=pypy-c-jit-linux-x86-64&branch=default I tracked this down to the test_setrlimit() test in test_lib_pypy/test_resources.py, skipping that test removes the SIGKILL failure Matti
Hi Matti, On 24 August 2016 at 14:08, Matti Picus <matti.picus@gmail.com> wrote:
Ah. As it turns out, the fix I did for OS/X applies here too. It should work from the next run, hopefully. (It got a crash because it called set_rlimit() with (0, 0), which instantly killed the process because it was using more than 0 seconds of CPU.) A bientôt, Armin.
The builds are ready and buildbots green (enough IMO). http://buildbot.pypy.org/nightly/release-5.x, any of the 86635-77392ad26350 binaries should be good to go. Please download and test them, especially the OSX and ARM ones. Anyone who is proficient with scipy/pandas/matplotlib could try their test suites out, upstream numpy should install on all platforms although there are known shortcomings with new buffer interface compatibility. I will be unable to repackage and upload to bitbucket for the next few days, so if anyone with fast internet can run the repackages script it would be very helpful: - update your pypy repo on linux - create a tmp directory anywhere in the repo - run pypy/tools/release/repackage.sh - upload the resulting 10 binary packages (8 precompiled, 2 source) to bitbucket/pypy/pypy/downloads - update pypy.org/downloads with the hashes printed out at the end of the script, or post them here We do not have ppc builds, so those would be helpful too. Thanks, and thanks to the team for pushing PyPy forward! Matti
Hi Matti, On 29 August 2016 at 01:14, Matti Picus <matti.picus@gmail.com> wrote:
Thanks for the work! The hg tag you created: "Added tag release-pypy2.7-v5.4.0 for changeset 68bb3510d821", is a changeset from default. Is that expected? Didn't you mean to use 77392ad26350?
We do not have ppc builds, so those would be helpful too.
I'm building them now. A bientôt, Armin.
On 30/08/16 19:10, Armin Rigo wrote:
https://bitbucket.org/pypy/pypy/downloads. If no-one complains in the next day or so I will finish the release. Matti
participants (3)
-
Armin Rigo -
David Edelsohn -
Matti Picus