Conversation
|
I think we should stop couchbase testing and eventually remove it from the build. I am not sure how much popular it is. |
968dd76 to
5b0a979
Compare
Yep! Working now to fix them. |
5b0a979 to
c0ca554
Compare
|
This pull request introduces 1 alert and fixes 2 when merging c0ca554 into 3384937 - view on LGTM.com new alerts:
fixed alerts:
|
@thedrow I've ran it 4 times in docker and so far it has always passed. I'm not sure how to trigger reruns with the github actions, but I haven't seen that error pop up yet. I'm assuming it's this one: #6489 |
|
Was able to recreate #6489. Will reopen after I fix it. |
c0ca554 to
3712de6
Compare
|
This pull request introduces 1 alert and fixes 2 when merging 3712de6 into cfa1b41 - view on LGTM.com new alerts:
fixed alerts:
|
|
Those dockerfile changes @mjhoffman65 mentioned might make life easier, but I don't see a ref to them. In any case, I've got a pypy3 interpreter on my box so I'll see if I can clean this up. |
|
Rebased this to hopefully fix the CI failures on that delivery info test, also with the correct fix for #6489 Edit: Annoyingly couchbase now doesn't appear to be And there's another test breaking under pypy3 in We could cherry pick 651a0ed by itself but I'm not confident enough to spend more time on this in the lead up to 5.1. |
|
This pull request fixes 3 alerts when merging 82d7ad3 into 426a8f9 - view on LGTM.com fixed alerts:
|
|
It's still broken :( I de-drafted this thinking it would run through and go green and now can't work out how to put it back 😬 Edit: Found it. It was a text link under the reviewers rather than a nice button... |
82d7ad3 to
19a4c33
Compare
|
Freshened this on top of master now that 5.1 is released. I've also made some changes to the workflow to run unit tests using tox. I think that might fix up some of the weirdness around the missing dependencies. We'll see... |
|
This pull request fixes 2 alerts when merging 4dd514e into 025bad6 - view on LGTM.com fixed alerts:
|
Mocking `datetime.datetime` was causing an issue with `datetime.utcnow()`. This mock doesn't appear to be needed. See https://github.com/celery/celery/pull/6635/checks?check_run_id=1944166896.
4dd514e to
a3b2af7
Compare
|
Freshened on master and also with a few extra fixes for the same kind of I'm hoping this will go green now, with the fix from #6806 pulled in via the rebase as well. |
Codecov Report
@@ Coverage Diff @@
## master #6635 +/- ##
==========================================
+ Coverage 70.70% 75.82% +5.12%
==========================================
Files 138 138
Lines 16603 16603
Branches 2092 2092
==========================================
+ Hits 11739 12590 +851
+ Misses 4668 3797 -871
- Partials 196 216 +20
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
Huh, weird, it's trying to run flake8 under action environments without python 3.9 installed :/ Edit: Oh 0295d7a did that. Probably no point in linting in each of the build jobs though, that's kind of weird |
|
This pull request introduces 1 alert and fixes 1 when merging a3b2af7 into d9d8250 - view on LGTM.com new alerts:
fixed alerts:
|
60a8122 to
1ce3b20
Compare
Also fix some flakes which may have been added by some other autoformatter in celery#6804. The 4 space non-visual-indentation should keep most formatters fairly happy.
1ce3b20 to
f486c0d
Compare
|
This pull request fixes 1 alert when merging f486c0d into d9d8250 - view on LGTM.com fixed alerts:
|
* installs packages the same way docker does * removes couchbase dependency for PyPy * removes ephem dependency for PyPy * fixes mongo unit tests for PyPy3 Mocking `datetime.datetime` was causing an issue with `datetime.utcnow()`. This mock doesn't appear to be needed. See https://github.com/celery/celery/pull/6635/checks?check_run_id=1944166896. * fix: Avoid shadowing `Thread` attributes Fixes celery#6489 * ci: Install default deps for pypy3 toxenvs * ci: Run unit tests with `tox` * ci: Lint source in separate action using `tox` * ci: Redent codecov action * test: Rework some mocking in `test_platforms.py` Also fix some flakes which may have been added by some other autoformatter in celery#6804. The 4 space non-visual-indentation should keep most formatters fairly happy. * style: Fix some flakes Co-authored-by: maybe-sybr <58414429+maybe-sybr@users.noreply.github.com>
@auvipy, I took at stab at fixing the PyPy failures. My first step is to try to install all the requirements and recreate the unit test failure in the docker environment. I ran into issues installing the python requirements and am wondering if more work needs to be done before we can expect celery to run with PyPy. Looks like at least a couple of the dependencies do not work with PyPy since they rely on a C backend.
couchbase: https://docs.couchbase.com/python-sdk/current/hello-world/start-using-sdk.html#pypy-support
ephem: celery/django-celery-beat#69 (comment) (Note we may be able to replace this with skyfield. See here for more.)
This PR illustrates the same error I'm getting in the docker environment: https://github.com/celery/celery/runs/1930241932?check_suite_focus=true
How should I move forward?