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
lritter has quit [Ping timeout: 264 seconds]
mgorny has quit [Quit: No Ping reply in 60 seconds.]
<felixphew>
Hi - bit of a weird question: what's the simplest way to run tests against the pypy source tree, specifically the hypothesis tests?
<felixphew>
I'm not trying to test pypy so much as I'm trying to create a little reference suite for hypothesis, and pypy is a nice "big" project that appears to make substantial use of hypothesis tests
<tumbleweed>
there are several different test suites that use hypothesis
<felixphew>
I'm running into some mechanical issues trying to run the tests. "pytest -D -m hypothesis pypy", which is the approach I'd normally take, is giving me (different) errors regardless of whether I run it under CPython 3.9 or PyPy 3.6
<fijal>
ok, any pointers how do I adapt the squeaky's portable setup to arm64?
<mattip>
ahh. I missed the "arm64" bit. So you would need to build the docker image in buildbot/docker,
<mattip>
then translate,
<mattip>
then run the packge.py script with the flag for portable so it adds the RPATH bits
<mattip>
the buildbot is ubuntu 18.04.3, if that libffi is good enough for you maybe you can just run package.py on the buildbot without a docker image?
<mattip>
hmm, the download page is wrong, the arm64 tarballs are not portable