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
jacob22 has quit [Read error: Connection reset by peer]
KindOne has quit [Quit: K-Lined]
jacob22 has joined #pypy
xcm has quit [Ping timeout: 260 seconds]
xcm has joined #pypy
KindOne has joined #pypy
inhahe_ has joined #pypy
inhahe has quit [Ping timeout: 240 seconds]
lritter has joined #pypy
jcea has quit [Quit: jcea]
jvesely has quit [Quit: jvesely]
jvesely has joined #pypy
andi- has quit [Ping timeout: 272 seconds]
KindOne has quit [Ping timeout: 265 seconds]
KindOne has joined #pypy
KindTwo has joined #pypy
KindOne has quit [Ping timeout: 272 seconds]
andi- has joined #pypy
KindTwo is now known as KindOne
dddddd has quit [Ping timeout: 258 seconds]
thrnciar has joined #pypy
marvin_ has quit [Remote host closed the connection]
marvin_ has joined #pypy
lazka has quit [Quit: bye]
lazka has joined #pypy
tsaka_ has quit [Ping timeout: 265 seconds]
<mattip> topic branches strike again: the buildbots do not have topic installed so we cannot trigger a build on them
tsaka_ has joined #pypy
tsaka_ has quit [Ping timeout: 260 seconds]
<arigo> :-/
<mjacob> i thought georges solved that problem at the sprint?
<mattip> the buildbot master knows about them, but not the slaves
<mattip> I think heptapod will hide the commits from hg clients without topic enabled
<mattip> anyhow I worked around it by making the branch a permanent one
xcm has quit [Killed (card.freenode.net (Nickname regained by services))]
xcm has joined #pypy
<mjacob> mattip: if the server is configured to do so, clients without the topic extension won't pull topics by default. but if they pull a specific revision ("hg pull -r ..."), they can pull topics.
xcm has quit [Killed (tepper.freenode.net (Nickname regained by services))]
xcm has joined #pypy
tsaka_ has joined #pypy
tsaka_ has quit [Quit: Konversation terminated!]
<mattip> mjacob: thanks
BPL has joined #pypy
<mattip> mjacob: it turns out we hacked the Mercurial buildbot class to specifically avoid doing that,
<mattip> since pulling a commit like that would break the semantic version numbering nnnn:xxxxxxxxxx
<mattip> where nnnn is the commit number and xxxx is the hash
<mattip> By pulling a single commit, the different rpython/own/jit build repos would have different nnnn numbers
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5079 [mattip: force build, issue3420]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5079 [mattip: force build, issue3420]
<arigo> I must say I'm dubious about the whole idea of topic branches and heptapod's "merge" model where people can't make forks
oberstet has joined #pypy
<arigo> ah
<mattip> it may make sense for cffi to move to gitlab/github, the number of long-lived branches is lower than pypy,
<mattip> and the chances for drive-by contributions is higher
xcm has quit [Read error: Connection reset by peer]
xcm has joined #pypy
dddddd has joined #pypy
<arigo> right
<mjacob> mattip: imho it's a good idea to stop using nnnn: in any case
lritter has quit [Ping timeout: 256 seconds]
<arigo> mjacob: I agree, but it's not clear what to use instead
marmoute_ is now known as marmoute
simpson has quit [Remote host closed the connection]
simpson has joined #pypy
slavfox has left #pypy [#pypy]
<mjacob> arigo: the hash?
<mjacob> seemingly there's something i'm missing
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5081 [mattip: force build, issue3420]
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5081 [mattip: force build, issue3420]
jacob22 has quit [Quit: Konversation terminated!]
jacob22 has joined #pypy
xcm has quit [Read error: Connection reset by peer]
xcm has joined #pypy
<mattip> mjacob: the commit number provide a loose ordering, and appear all through the buildbot codebase
<mattip> the problem is on a practical level what we would replace them with, and who is going to go through the code and do it
<mattip> we could sort by date, or always look up the number on the master's repo, or ...
<arigo> maybe adding a number derived from the date of the commit would be enough?
dansan has joined #pypy
<bbot2> Started: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5083 [mattip: force build, issue3240]
thrnciar has quit [Ping timeout: 272 seconds]
jcea has joined #pypy
xcm has quit [Ping timeout: 265 seconds]
tsaka__ has joined #pypy
thrnciar has joined #pypy
xcm has joined #pypy
<bbot2> Failure: http://buildbot.pypy.org/builders/pypy-c-jit-macosx-x86-64/builds/5083 [mattip: force build, issue3240]
tsaka__ has quit [Ping timeout: 265 seconds]
tsaka__ has joined #pypy
KindTwo has joined #pypy
KindOne has quit [Ping timeout: 272 seconds]
KindTwo is now known as KindOne
xcm has quit [Ping timeout: 272 seconds]
xcm has joined #pypy
KindTwo has joined #pypy
KindOne has quit [Ping timeout: 256 seconds]
KindTwo is now known as KindOne
xcm has quit [Ping timeout: 246 seconds]
xcm has joined #pypy
xcm has quit [Killed (kornbluth.freenode.net (Nickname regained by services))]
xcm has joined #pypy
BPL has quit [Quit: Leaving]
jacob22 has quit [Remote host closed the connection]
jacob22 has joined #pypy
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
oberstet has quit [Quit: Leaving]