Warning
The code base for this project is under heavy and recent development. Please expect nothing from it for the time being; there is not yet a version that we consider "stable".
...
- GNU Make (Anything reasonably recent)
- GNU g++ (>= 4.4.6)
- git (>= 1.6.0)
- Perl (Anything reasonably recent)
- For mergedeps.pl, which automatically inserts included headers in source files into the make dependencies.
- Python 2.6, epydoc
- Boost
- If you're having issues with Boost on Ubuntu, check boost ticket #3844.
- pcre
- Doxygen 1.7.2
- protocol buffers
...
- No commit should include changes for multiple issues. (Each commit in the push should complete or work towards a single issue.)
- Pushes should complete any issues they start, but individual commits within a push do not need to complete an issue.
- All commit messages should be meaningful without looking at the diff. (By reading a commit message, you should get some idea of what was modified and what the intent was. If you can't fit this in one line, skip a line and then write more.)
Running Under Valgrind
Use make VALGRIND=yes testCompiling unit test:
| No Format |
|---|
make VALGRIND=yes test |
Running unit test: The 'master' part in 'obj.master' could be replaced your git branch name.
| No Format |
|---|
valgrind --leak-check=yes obj.master/test |
Running system test with valgrind: Now extending 'scripts/cluster.py' which post RAMCloud tasks into the server cluster.
Additional Sanity Checks
Before pushing to the master branch on fiz it is generally a good idea to make sure your changes haven't caused regressions in the recovery system.
...