On Sun, Apr 1, 2012 at 3:48 PM, Stefan Behnel <stefan...@behnel.de> wrote: > Maciej Fijalkowski, 01.04.2012 15:42: >> On Sun, Apr 1, 2012 at 3:25 PM, Maciej Fijalkowski wrote: >>> On Sun, Apr 1, 2012 at 3:04 PM, Stefan Behnel wrote: >>>> Armin Rigo, 01.04.2012 12:31: >>>>> Hi Stefan, >>>>> >>>>> Done in 623bcea85df3. >>>> >>>> Thanks, Armin! >>>> >>>> Would have taken me a while to figure these things out. >>>> >>>> I'll give it a try with the next nightly. >>> >>> You can create your own nightly by clicking "force build" on the buildbot. >> >> Ah, maybe worth noting is that -jit are ones that create nightlies >> that you're interested in. I'll cancel the other ones. > > Right, it's not immediately obvious which build job triggers what kind of > output. I'm currently using the nojit version because it hand-wavingly > appeared more stable than the jit version so far, and I doubt that there's > any benefit for us to test against a jit build. Specifically, I'm > interested in this file: > > http://buildbot.pypy.org/nightly/trunk/pypy-c-nojit-latest-linux64.tar.bz2 > > Stefan > > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev
It's totally not :) Then it's the applevel one. I'll poke it. _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
