The peace of green
No, we are not going to talk about the environment (i.e., the set of variables as printed by /usr/bin/env. What else? :-)).
After months in which we had a couple of tests failing every day, we finally managed to turn (almost) everything green today, at least on Linux. Enjoy this screenshoot taken from the nightly build page:
As usual, the full buildbot results can be seen from the summary page.
cheers, Anto
The PyPy blogposts
Create a guest post via a PR to the source repo
Recent Posts
- Guest Post: Final Encoding in RPython Interpreters
- A DSL for Peephole Transformation Rules of Integer Operations in the PyPy JIT
- Guest Post: How PortaOne uses PyPy for high-performance processing, connecting over 1B of phone calls every month
- PyPy v7.3.17 release
- Conda-forge proposes sunsetting support for PyPy
- A Knownbits Abstract Domain for the Toy Optimizer, Correctly
- Abstract interpretation in the Toy Optimizer
- Mining JIT traces for missing optimizations with Z3
- Finding Simple Rewrite Rules for the JIT with Z3
- Profiling PyPy using the Firefox profiler user interface
Archives
Tags
- arm (2)
- casestudy (3)
- cli (1)
- compiler (1)
- conda-forge (1)
- cpyext (4)
- CPython (3)
- ep2008 (1)
- extension modules (3)
- gc (1)
- guestpost (2)
- GraalPython (1)
- hpy (1)
- Heptapod (1)
- jit (23)
- jython (1)
- kcachegrind (1)
- meta (1)
- numpy (24)
- parser (1)
- performance (2)
- profiling (4)
- pypy (6)
- pypy3 (16)
- PyQt4 (1)
- release (62)
- releasecffi (3)
- releaserevdb (1)
- releasestm (1)
- revdb (1)
- roadmap (2)
- RPyC (1)
- speed (6)
- sponsors (7)
- sprint (3)
- sprints (1)
- stm (14)
- sun (1)
- Smalltalk (1)
- Squeak (1)
- testing (1)
- toy-optimizer (4)
- unicode (1)
- valgrind (1)
- z3 (5)
Comments
Am I sensing a PyPy 1.4 release?
@intgr: "yes", although we don't have any concrete plan to do a release. But it's true that if we keep all our tests green, doing a release it's much less effort