Task #4500: Collect test coverage from rq workers - Pulp

Actions

Send by e-mail Copy link

Task #4500

closed

Collect test coverage from rq workers

Added by daviddavis about 5 years ago. Updated almost 3 years ago.

Status:

CLOSED - WONTFIX

Priority:

Normal

Assignee:

Category:

Sprint/Milestone:

Start date:

Due date:

% Done:

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

This is a task to revisit this PR:

https://github.com/pulp/pulpcore/pull/10

We had to revert these changes because it doubled the build time from 20 to 40 min.

Related issues

Actions

Copy link

Updated by daviddavis about 5 years ago

Related to Issue #4499: Pulpcore Travis builds are taking twice as long (40 min vs 20 min) added

Actions

Copy link

Updated by amacdona@redhat.com about 5 years ago

I like the idea of running this nightly instead of each PR. That will do less for encouraging high coverage, but we were mostly ignoring that anyway.

Actions

Copy link

Updated by daviddavis about 5 years ago

Related to Refactor #4416: Gather coverage from Content app for test purposes added

Actions

Copy link

Updated by bmbouter about 5 years ago

I asked about this to the RQ community in their issue tracker here: https://github.com/rq/rq/issues/1051

Their suggestion is to use the SimpleWorker which will run the RQ tasks in the webserver itself synchronously. We could try to have a new worker type pulpcore.tests.functional.worker_with_coverage.CoveragePulpWorker that would use SimpleWorker with our custom worker behaviors from PulpWorker.

Actions

Copy link