ci: Fix pypy3 CI #6417
ci: Fix pypy3 CI #6417
Conversation
|
I've put in a speculative integration test against a rabbitmq backend to see if it works. It's not really necessary to fix #6409 but can't hurt if it works (except chew CI time, so happy for it to be vetoed based on that as well). |
|
Looks like the unit tests were fine but one of my integration tests from #6354 timed out. Probably needs a bit of digging to work out if it's actually broken or just flaky on pypy3 for some reason. I don't have the time to dig into it right now so I'd be fine with stripping the integration test job out of this changeset and just fixing the unit tests for now. LMK what you'd like to do and I can amend the branch. |
maybe-sybr
force-pushed
the
maybe/ci-correct-pypy3-toxenv
branch
from
978d524
to
8843abb
Compare
|
@auvipy I've stripped the commit which added the breaking integration test for now. I can look at that at some later point, for now getting pypy3 unit tests running is a good start. https://github.com/maybe-sybr/celery/tree/maybe/ci-pypy3-integration if anyone is interested in following up/stealing that branch from me. |
This changeset fixes the TOXENV for pypy3 unit tests in travis and adds
rabbitmq integration tests against pypy3 as well like we do for Python 3.9.