Skip to content

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

Switch branch/tag
  • darshan
  • darshan-test
  • example-output
  • mpi-io-test-ppc64-3.1.4.darshan
Find file
HistoryPermalink
  • Shane Snyder's avatar
    replace old example output that didn't include dxt · db84851e
    Shane Snyder authored Jan 09, 2018
    we should probably always include logs that contain dxt data in
    the example output directory so we can track that module over
    releases
    db84851e
mpi-io-test-ppc64-3.1.4.darshan 1.72 KB

Download (1.72 KB)

Replace mpi-io-test-ppc64-3.1.4.darshan

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.