Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
D
darshan
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
62
Issues
62
List
Boards
Labels
Milestones
Merge Requests
5
Merge Requests
5
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
darshan
darshan
Commits
f3954869
Commit
f3954869
authored
Feb 04, 2015
by
Philip Carns
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
update README
parent
d3c4b9dd
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
10 deletions
+8
-10
README.txt
darshan-test/regression/README.txt
+8
-10
No files found.
darshan-test/regression/README.txt
View file @
f3954869
This directory contains regression tests for both the runtime and util components of Darshan,
assuming that Darshan is already compiled and installed in a known path.
This directory contains regression tests for both the runtime and util
components of Darshan, assuming that Darshan is already compiled and
installed in a known path.
The master script must be executed with three arguments:
1) path to darshan installation
2) path to temporary directory (for building executables, collecting logs, etc. during test)
2) path to temporary directory (for building executables, collecting logs,
etc. during test)
3) platform type; options include:
- ws (for a standard workstation)
The platform type should map to a subdirectory containing scripts
that describe how to
perform platform-specific tasks (like loading or generating darshan wrappers and executing
jobs).
The platform type should map to a subdirectory containing scripts
that describe how to perform platform-specific tasks (like loading or
generating darshan wrappers and executing
jobs).
TODO:
---------
- tie this in with the "automated" directory in the tree, which already performs automated
build tests (but no runtime tests) in Jenkins
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment