Difference between revisions of "Developer Documentation"
From Mpich
(starting a cray page) |
|||
| Line 2: | Line 2: | ||
** [[Building MPICH For Development]] | ** [[Building MPICH For Development]] | ||
*** [[BGQ|Blue Gene/Q]] | *** [[BGQ|Blue Gene/Q]] | ||
| + | *** [[Cray|XC40]] | ||
* [[Contributing to MPICH]] - '''Please Read Before Contributing''' | * [[Contributing to MPICH]] - '''Please Read Before Contributing''' | ||
** [[Version Control Systems 101]] | ** [[Version Control Systems 101]] | ||
Revision as of 14:17, 9 May 2018
- Getting And Building MPICH
- Contributing to MPICH - Please Read Before Contributing
- Creating New Bug Tickets
- Using the Hydra Process Manager
- Checkpointing
- Student Projects
- Tools
- Frequently Asked Questions
- ABI Compatibility Initiative
- Testing
- Nightly Tests
- Special Tests - These tests are run manually, usually as part of gearing up for a release. Be sure to look at the date to make sure that you aren't looking at stale results. Information on running the special tests is at Testing MPICH#Running the Special Tests.
- Jenkins is used to run a number of test configurations on every push to certain Git repositories. See that page for more information.
- Writing New Tests
- Testing Crons
- Code Coverage Reports
- MPICH ABI Tests
- Design Docs: Category:Design Documents
- Miscellaneous
- Using etags on the MPICH source tree
- Mailing lists
- Bug Tracking
- Recent Changes
- Fixing Bugs in Released Code
- Rules For Installation Targets
- Adding New Error Messages
- Creating a Release
- Managing Commits in Trunk and Release Branches
- Proposed MPIEXEC Extensions such as a standard set of command-line options for environment variables and support for multi-threaded applications.
- A list of assorted Compiler Quirks to be aware of.
- Creating MPICH Manpages
- Auto-generated pages
