Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • spam spam
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ttk
  • spamspam
  • Issues
  • #184

Closed
Open
Created Oct 11, 2020 by Gustavo Pinzon@pinzonfgMaintainer

Coverage and multiprocessing

When running the test for spam.label.moveLabes(), the test is running but the coverage report is not showing the evaluation of the worker. Adding --concurrency=multiprocessing && coverage combine to python setup.py install && coverage run --concurrency=multiprocessing setup.py test && coverage combine && coverage html solves the issue (the worker is excluded from the coverage), but the file spam.visual.visualClass.py is not excluded and tested (under normal operation the file is excluded in the coverage report). On previous functions with multiprocessing, the worker is excluded in the coverage report.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking