Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #5

Closed
Open
Opened Sep 24, 2015 by Shane Snyder@ssnyder
  • Report abuse
  • New issue
Report abuse New issue

Collisions on darshan generated file name

Ray Loy reported this with cobalt-subrun but could also happen in a normal mpirun environment.

Jobs started with cobalt-subrun all have the same jobid and user and possibly the same start/end time to the second resolution. This will cause one darshan log to be written but other mpiruns will have errors in the standard error complaining that the darshan log could not be written.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
defect wrapper libraries
Assign labels
  • View project labels
Reference: darshan/darshan#5