Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • tapasco tapasco
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 52
    • Issues 52
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tapascotapasco
  • tapascotapasco
  • Issues
  • #92
Closed
Open
Issue created Jun 02, 2017 by Jens Korinth@jkDeveloper

Do not run HLS in DSE for existing cores

The DSE tasks starts HLS for all kernels and targets in the job; the HLS task will exit quickly on a regular machine, but when run with SLURM this incurs unnecessary compute time for the additional jobs. Fix by running HLS only for those kernels and targets, where no core yet exists (see Compose).

Assignee
Assign to
Time tracking