antocuni changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | "PyPy: the Gradual Reduction of Magic (tm)"
adamholmberg has quit [Read error: No route to host]
adamholmberg has joined #pypy
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
BlackVegetable has joined #pypy
BlackVegetable has left #pypy [#pypy]
adamholmberg has quit [Read error: Connection reset by peer]
adamholmberg has joined #pypy
adamholm_ has joined #pypy
adamholmberg has quit [Ping timeout: 248 seconds]
jcea has quit [Read error: Connection reset by peer]
jcea has joined #pypy
adamholmberg has joined #pypy
marr has quit [Ping timeout: 255 seconds]
adamholm_ has quit [Ping timeout: 252 seconds]
zmt00 has joined #pypy
<kenaan>
antocuni default b015a2924278 /pypy/module/_continuation/test/test_stacklet.py: improve this test by using the same 'seen' pattern also used by other tests, so that it's easier to follow the c...
<kenaan>
antocuni cpyext-avoid-roundtrip a1ed00dd3eba /pypy/module/cpyext/typeobject.py: kill this check; all the tests pass
<antocuni>
arigato: ping? I'm trying to understand continulet and I'd like some guidance :)
<antocuni>
from what I understood so far, if I have a function foo(c, ...), where c is the continulet
<antocuni>
when I do "c.switch()", is basically the same as doing "return-but-I-will-be-able-to-be-resumed-later"
forgottenone has joined #pypy
<antocuni>
i.e., after I do c.switch() I always return to the "caller", where "caller" == "the line which called the .switch() which started/resumed me"
<antocuni>
is it correct so far, or I am missing something?
exarkun has quit [Read error: Connection reset by peer]
marky1991 has quit [Remote host closed the connection]
marky1991 has joined #pypy
exarkun has joined #pypy
raynold has joined #pypy
<kenaan>
antocuni default 1c3af3c4a095 /pypy/module/_continuation/test/test_stacklet.py: improve this test by giving more descriptive names to variables; in particular, f vs f* was a bit confusing, at ...
realitix has joined #pypy
Arfrever has joined #pypy
realitix has quit [Quit: Leaving]
cstratak has quit [Quit: Leaving]
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
marky1991 has quit [Read error: Connection reset by peer]
tbodt has joined #pypy
marky1991 has joined #pypy
oberstet has quit [Ping timeout: 240 seconds]
inad922 has quit [Ping timeout: 255 seconds]
antocuni has quit [Ping timeout: 248 seconds]
oberstet has joined #pypy
inad922 has joined #pypy
inad922 has quit [Ping timeout: 246 seconds]
exarkun has quit [Ping timeout: 255 seconds]
marky1991 has quit [Read error: Connection reset by peer]
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<mattip>
dw: any conclusions about the too slow macosx buildbot?
<dw>
mattip: it's going to take me some time
<mattip>
ok. Anything we can do to make it easier?
<dw>
mattip: sorry, hands full :/ i could just reboot the box again, but it's a lame fix because we'll just be having this conversation again in 2 months
<mattip>
bummer. Maybe worthwhile to kill the buildslave process, to keep from burning up your swap disk
<mattip>
we used to have more macosx slaves, at least there is one named tosh and another named rebuy-de listed
<dw>
it's not anything obvious with IO, need to actually _look_ at it , but i have $work for now
<dw>
is there no money in the jar for a managed box?
<dw>
seems a shame to be relying on me hehe
<dw>
mattip: give me a few days, stuff is busy just now. it worsens with uptime so it's somehing OS related, i'll find it
* mattip
feels bad for running your machine 24/7
forgottenone has quit [Ping timeout: 240 seconds]
<Rotonen>
macos runs relatively happily under qemu/kvm
<Rotonen>
one could try to do nested virtualization on a commodity provider (or rent cheap hardware and have a go at it)