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)"
tbodt has joined #pypy
antocuni has joined #pypy
yuyichao has quit [Ping timeout: 258 seconds]
marky1991 has joined #pypy
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
yuyichao has joined #pypy
tbodt has joined #pypy
tbodt has quit [Ping timeout: 240 seconds]
tbodt has joined #pypy
squeaky_pl has quit [Ping timeout: 264 seconds]
_whitelogger has joined #pypy
tbodt has joined #pypy
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 240 seconds]
antocuni has quit [Ping timeout: 240 seconds]
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
marky1991 has quit [Ping timeout: 240 seconds]
dmalcolm has quit [Ping timeout: 264 seconds]
marr has quit [Ping timeout: 255 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 248 seconds]
lritter has quit [Quit: Leaving]
tav has quit [Quit: tav]
tav has joined #pypy
tav has quit [Read error: Connection reset by peer]
tav` has joined #pypy
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 240 seconds]
ArneBab has joined #pypy
ArneBab_ has quit [Ping timeout: 260 seconds]
jcea1 has joined #pypy
jcea has quit [Read error: Connection reset by peer]
jcea1 is now known as jcea
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 240 seconds]
jcea has quit [Remote host closed the connection]
forgottenone has joined #pypy
Garen has quit [Read error: Connection reset by peer]
Garen has joined #pypy
_whitelogger has joined #pypy
adamholmberg has quit [Ping timeout: 240 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 258 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 255 seconds]
kushal has quit [Ping timeout: 248 seconds]
kushal has joined #pypy
kushal is now known as Guest39255
_whitelogger has joined #pypy
forgottenone has quit [Quit: Konversation terminated!]
zmt00 has quit [Ping timeout: 260 seconds]
slackyy has quit [Ping timeout: 248 seconds]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 240 seconds]
oberstet has joined #pypy
forgottenone has joined #pypy
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 240 seconds]
antocuni has joined #pypy
squeaky_pl has joined #pypy
<antocuni> how is it possible that rpython/rlib/rvmprof/test/test_file does NOT fail on buildbot?
marr has joined #pypy
<antocuni> the C files in the pypy repo are outdated w.r.t. the ones in the vmprof repo
<antocuni> and the test fails on my machine
<antocuni> test_rvmprof:test_enable and test_native are skipped because "vmprof unimportable"
<antocuni> but test_native actually fails, god knows since when
<antocuni> very very bad :(
<antocuni> ah, maybe I know about test_file; it does os.walk('rpython/rlib/rvmprof/src/shared'), which means that if the cwd is not the one the test expects, it will silently pass because it doesn't find any file
<kenaan> antocuni vmprof-0.4.10 4d73e43ae3fb /: a branch where to update the code to vmprof 0.4.10
<kenaan> antocuni vmprof-0.4.10 0317d4f69638 /rpython/rlib/rvmprof/test/test_file.py: bah, I think that this test did not actually test anything because on buildbot the cwd was different that ...
<kenaan> antocuni vmprof-0.4.10 526d9b94882a /rpython/rlib/rvmprof/test/test_rvmprof.py: I claim that tests should NEVER fail silently; I think that test_native actually fails on linux, but the b...
antocuni has quit [Ping timeout: 260 seconds]
<cfbolz> antocuni: thanks for caring for this
kipras`away is now known as kipras
antocuni has joined #pypy
adamholmberg has joined #pypy
<bbot2> Started: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/6345 [antocuni: force build, vmprof-0.4.10]
marr has quit [Ping timeout: 252 seconds]
adamholmberg has quit [Ping timeout: 240 seconds]
antocuni has quit [Ping timeout: 260 seconds]
<mjacob> antocuni: maybe at some point we should go through all the skipped tests and check whether they are failing for good reasons
<bbot2> Failure: http://buildbot.pypy.org/builders/own-linux-x86-64/builds/6345 [antocuni: force build, vmprof-0.4.10]
lritter has joined #pypy
kipras is now known as kipras`away
slackyy has joined #pypy
zmt00 has joined #pypy
mattip has joined #pypy
Garen has quit [Read error: Connection reset by peer]
Garen has joined #pypy
<kenaan> mattip default 1ea57a8b4a91 /pypy/module/zipimport/test/test_zipimport.py: whoops in 5c8b7f2cd6b7
<mattip> arigato: it seems indeed there is a 'uu' module at the time the build slave runs this test ^^^, but only in buildslave runs
<mattip> since I left 'uu' in the assert by mistake and the test failed last night
nunatak has joined #pypy
<kenaan> mattip default 9d22ff3be2ae /rpython/rlib/: graft parts of 287c9946859b that provide rposix.lockf in rpython
<kenaan> stian math-improvements f30c2f38b0b5 /rpython/rlib/: Make rshift invert (in most cases) in place, this makes a huge speedup for rshift with negative numbers a...
nunatak_ has joined #pypy
nunatak has quit [Ping timeout: 240 seconds]
nunatak_ is now known as nunatak
AndrewBC has quit [Quit: Leaving]
forgottenone has quit [Quit: Konversation terminated!]
<kenaan> rlamy default b97f900404e5 /extra_tests/: Add extra-tests for string methods, matching the interp-level tests added in 88bed3bb8ad4
tbodt has joined #pypy
<mattip> ronan: what is the motivation for extra_tests? It seems they duplicate other tests, no?
<ronan> mattip: the point is to have app-level tests that run directly on a translated pypy
<mattip> what is the advantage to the already-existing interp-level tests, are they instead-of or in-addition-to?
<ronan> it's mostly in-addition-to
<mattip> if we replicate all our interp-level tests we will make buildbot runs even more expensive
<mattip> as it is the ARM tests barely finish in 24 hours
<ronan> app-level tests are much cheaper than interp-level ones
<mattip> so the goal is to replace the more expensive ones?
<ronan> yes
<mattip> we would mark the replicant tests "slow" or "replicate" and run them only if the "fast" version fails
<mattip> ok, nice
<mattip> (if I understood correctly)
<ronan> I don't think we need to keep slow interp-level (or untranslated app-level) tests at all
<ronan> from an app-level failure, we can usually extract a *specific* interp-level test case
<mattip> that sounds good too
<kenaan> rlamy py3.5 a433b30d93a4 /: hg merge default
<kenaan> rlamy py3.5 186f4b89a84a /pypy/objspace/std/test/: Kill tests involving dodgy comparisons with CPython 2 and superseded by b97f900404e5
raynold has quit [Quit: Connection closed for inactivity]
tbodt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
tbodt has joined #pypy
marky1991 has joined #pypy
marr has joined #pypy
jcea has joined #pypy
marky1991 has quit [Ping timeout: 240 seconds]
raynold has joined #pypy
<kenaan> fijal unicode-utf8 a6e6ba074a22 /rpython/rlib/: * Return a flag from check_utf8. * Improve the tests and run it for more examples
<kenaan> fijal unicode-utf8 29ce3a4ea76f /: progress on having flags correctly propagated, almost there
<kenaan> fijal unicode-utf8 47de95da2bbb /: finish whacking until the objspace tests pass
<kenaan> fijal unicode-utf8 71debd44669a /pypy/module/: small fixes, for revisting later once we actually want tests to pass
<kenaan> fijal unicode-utf8 0c93ee971f62 /: first attempt at fixing the unicode surrogate mess
<kenaan> fijal unicode-utf8 94c9ccfbd63c /pypy/: fix enough to pass all the tests in test_unicodeobject
<kenaan> fijal unicode-utf8 0aeb46cc86b0 /pypy/: whack enough to get somewhere with the list strategy - just for ascii-unicode so far
<kenaan> fijal unicode-utf8 1645f5285398 /pypy/: fight until the strategies seem to work again for ascii unicode strings at least
<kenaan> fijal unicode-utf8 4bd78617a41a /pypy/objspace/std/unicodeobject.py: add assertions for now
<kenaan> fijal unicode-utf8 ec7d2032eb70 /TODO: update TODO
<kenaan> fijal unicode-utf8 10e8aaa42286 /pypy/objspace/std/setobject.py: ups, fix
<fijal> sorry that was a long flight
nunatak has quit [Remote host closed the connection]
marky1991 has joined #pypy
glyph has quit [Quit: End of line.]
slackyy has quit [Ping timeout: 248 seconds]
glyph has joined #pypy
marky1991 has quit [Read error: Connection reset by peer]
marky1991 has joined #pypy
mattip has left #pypy ["bye"]
<fijal> uh
<fijal> why do we want tests to run if hypothesis is not installed?
<fijal> more and more tests are using it
<simpson> I have a stupid desire. I want to know all of the arguments to a particular input of a function at translation time. I know that the inputs are all constant at all call sites, I just don't want to read the source code in order to be able to ask the binary which ones it was compiled with.
<simpson> Can RPython help me out here, or do I have to annotate each call site by hand?
<fijal> simpson: yes, but it's not THAT easy to get out
<fijal> you need to stick a pdb somewhere
<fijal> in the annotator and get the callfamilies
<simpson> Hmmm. Maybe there's another way altogether. I have a conditional debug statement, and each call site lists some possible flags; if any flag is provided at runtime, then the debug statement should fire.
<simpson> So really what I want to do is get that list of flags into the CLI's help/usage wall of text.
slackyy has joined #pypy