Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK-m VTK-m
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 188
    • Issues 188
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • 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
  • VTK
  • VTK-mVTK-m
  • Merge requests
  • !1869

Closed
Created Sep 26, 2019 by Kenneth Moreland@kmorelMaintainer
  • Report abuse
Report abuse

Log information about entering and leaving device scope

  • Overview 5
  • Commits 1
  • Pipelines 1
  • Changes 1

I was running some rendering examples and I was surprised to see some log messages stating that my device was being forced to Serial. Panicked, I opened up a debugger and set a breakpoint where the device was forced to Serial. Turns out, the device was forced to Serial inside of a ScopedRuntimeDeviceTracker (as part of the ColorTable operation). However, the log gave no indication that the default devices were restored.

To prevent further misunderstandings for myself and others, added some log messages to the ScopedRuntimeDeviceTracker to write when the scope is entered and left at the same logging level as that of the announcement that the device is forced.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: log-scoped-device