cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
suhdonghwi[m] has joined #pypy
speeder39_ has joined #pypy
Taggnostr has quit [Ping timeout: 260 seconds]
lritter has joined #pypy
speeder39_ has quit [Quit: Connection closed for inactivity]
wilbowma has quit [Ping timeout: 240 seconds]
wilbowma has joined #pypy
rubdos has quit [Ping timeout: 246 seconds]
rubdos has joined #pypy
glyph has quit [Quit: End of line.]
glyph has joined #pypy
<mgorny> i'm getting the hang of merges with mercurial
<mgorny> still, i hate it
Taggnostr has joined #pypy
<mgorny> i'm done resolving merge conflicts
<mgorny> now ensurepip
<mgorny> *beeeep*
<mgorny> it seems that mercurial didn't commit the changes to the branch :-(
<mgorny> ok, managed to move it, i think
lritter has quit [Ping timeout: 246 seconds]
wilbowma has quit [Ping timeout: 240 seconds]
wilbowma has joined #pypy
tos9_ is now known as tos9
swills has joined #pypy
rubdos has quit [Ping timeout: 246 seconds]
rubdos has joined #pypy
mattip has joined #pypy
<mattip> mgorny: should we kick a build of stdlib-2.7.18-3 ?
<mgorny> yes, please
<mgorny> also, i might have screwed something up with that macosx topic
<mgorny> but i really have no clue what hg did there or why
<mgorny> (it looks like it recreated it or sth?)
<mattip> which topic? In general if you have topics enabled, you should use hg push -r <specific-branch-head>
<mattip> rather than vanilla hg push
<mattip> otherwise it ends up pushing things that probably should not be pushed
<mattip> for kicking buildbots, I find it easiest to go to http://buildbot.pypy.org/builders,
<mattip> scroll down to the "Force Build" section, fill in the form and hit 'Force Build'
<mattip> for a stdlib change, all we care about are "pypy-c-jit-*" builds
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-aarch64/builds/672 [mattip: test branch, stdlib-2.7.18-3]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6032 [mattip: test branch, stdlib-2.7.18-3]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/1400 [mattip: test branch, stdlib-2.7.18-3]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5235 [mattip: test branch, stdlib-2.7.18-3]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7225 [mattip: test branch, stdlib-2.7.18-3]
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/5551 [mattip: test branch, stdlib-2.7.18-3]
<mattip> like that :)
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-32/builds/6032 [mattip: test branch, stdlib-2.7.18-3]
<mgorny> heh, i thought they were supposed to get fired automatically, and that's why you asked specifically for a branch
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/7225 [mattip: test branch, stdlib-2.7.18-3]
<mgorny> hmm, how could i have missed that import
<mgorny> lemme run them locally first, this time
<mgorny> damn, it doesn't like my installed pypy executable :-(
<tumbleweed> /35/34
<tumbleweed> grr
<mgorny> mattip: fyi, i've just gotten a report that pypy2.7 7.3.2 segfaults on ppc64 (7.3.1 was fine)
<mgorny> the reporter is currently trying to collect some helpful information
<mgorny> thanks, i'll pass that on
_whitelogger has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/5551 [mattip: test branch, stdlib-2.7.18-3]
tos9 has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
tos9 has joined #pypy
<mattip> mgorny: since builds take over 2 hours, and we are using borrowed machines, we don't kick too much automatically
<mattip> if we could hook up travis or azure to foss.heptapod.net ...
<mgorny> mattip: not sure if they wouldn't timeout
<mgorny> ok, so i'll try to fix the tests locally first
<mgorny> and then i'll fire buildbots
<mattip> cool thanks
<mgorny> mattip: the correct thing to do is to commit fixes into the stdlib-* integration branch, correct?
<mattip> yes
<mattip> theoretically they should get a comment with PyPy in it, so we can track the difference to upstream,
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-s390x/builds/1400 [mattip: test branch, stdlib-2.7.18-3]
<mattip> but since in this case upstream has officially closed the 2.7 branch, it is now just nice to have
<mgorny> mattip: yes, i'm trying to add them when i notice we've diverged
<mgorny> it's helpful when you merge new stuff
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5235 [mattip: test branch, stdlib-2.7.18-3]
<mattip> > not sure if they wouldn't timeout: we should split the pypy-c-jit-* runs
<mattip> into translation as one run, and test as another
<mattip> that would allow stdlib/lib_pypy changes to be tested quickly
<mgorny> yeah, i've split gentoo packages like that
<mgorny> there's one package that delivers pypy-c executable and the few generated includes
<mgorny> and another that installs and tests stdlib
<mattip> I think we have this in the code, "just" need to reconfigure the build steps
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-linux-aarch64/builds/672 [mattip: test branch, stdlib-2.7.18-3]
jcea has quit [Remote host closed the connection]
jcea has joined #pypy
lritter has joined #pypy
jcea has quit [Remote host closed the connection]
jcea has joined #pypy
gsnedders has quit [Remote host closed the connection]
gsnedders has joined #pypy
jacob22 has quit [Quit: Konversation terminated!]
jacob22 has joined #pypy