Will be used by the indexers.
Details
- Reviewers
douardda ardumont - Group Reviewers
Reviewers - Commits
- rDSCH762b5283e1cc: Add SchedulerTestFixture.
There's a test included
Diff Detail
- Repository
- rDSCH Scheduling utilities
- Branch
- SchedulerTestFixture
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 1971 Build 2383: tox-on-jenkins Jenkins Build 2382: arc lint + arc unit
Event Timeline
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSCH/job/tox/12/
See console output for more information: https://jenkins.softwareheritage.org/job/DSCH/job/tox/12/console
swh/scheduler/celery_backend/runner.py | ||
---|---|---|
38–68 | There should be at least an explanation about why this refactoring in the celery runner is required to add a test fixture, and give a clue what's going one in this refactoring. Besides, you de facto change the API of the run_ready_tasks function so this must be documented in the doc string and the rationals for this API change should be explained in the commit message. |
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSCH/job/tox/13/
See console output for more information: https://jenkins.softwareheritage.org/job/DSCH/job/tox/13/console
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DSCH/job/tox/14/
See console output for more information: https://jenkins.softwareheritage.org/job/DSCH/job/tox/14/console
Build is green
See https://jenkins.softwareheritage.org/job/DSCH/job/tox/15/ for more details.
swh/scheduler/celery_backend/runner.py | ||
---|---|---|
93 | If I am understanding this correcly, that will become quite large... (as in too large, MemoryError) [1] https://grafana.softwareheritage.org/d/LmGkNMNik/sofwareheritage-scheduler?orgId=1 |
swh/scheduler/celery_backend/runner.py | ||
---|---|---|
93 | Ah but as you pointed out, there is the boundary (max_queue_length and all that ;). |
swh/scheduler/tests/test_fixtures.py | ||
---|---|---|
16 | Why not use swh.scheduler.tasks here since that will reflect the actual reality of what we run? |
Sounds good.
Tests fine through tox.
swh/scheduler/tests/test_fixtures.py | ||
---|---|---|
39 | Using swh.scheduler.utils.create_task_dict? That'd make one more entrypoint used by tests ;) |
Build is green
See https://jenkins.softwareheritage.org/job/DSCH/job/tox/16/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DSCH/job/tox/17/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DSCH/job/tox/26/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DSCH/job/tox/27/ for more details.