This was some kind of memory usage analysis tool. It depends on the control
port so it cannot work after I delete the control port. The code itself is
messy, undocumented, and has no automated tests. I don't know if it works at
all anymore. Even if it does, no one ever runs it.
Measuring Tahoe-LAFS' memory usage over the course of maintenance and
development is a lovely idea but the project has not managed to adopt (or
maintain?) that practice based on this tool. Given sufficient interest we can
resurrect this idea using a more streamlined process and less invasive tools
in the future.
- Use the subunitv2-file reporter to allow for nicer error handling
- Undo the depgraph.sh change, see if it really matters
- Rename passing -> ratchet-passing to distinguish from ported modules
tracker
- Misc. documentation and ratchet.sh improvements
We no longer need the complexity of choosing the application name at
runtime. This removes the setup.py code which populates the _appname.py
file, and the code in __init__.py which reads it. It does not yet remove
the tests which compare the output of e.g. `tahoe --version` against
`allmydata.__appname__`, which I think could be removed, but that's more
invasive than I want to do right now.
closes ticket:2754
Run with "tox -e coverage". Uses a new helper
module (allmydata.test.run_trial) to let us import+execute trial without
knowing exactly where the "trial" binary lives, which helps with using
"coverage run" under tox.
So use 'tox -e check-memory' instead of 'make check-memory'. The tox
version will create a virtualenv and install tahoe for you before
running the tests, removing one use of the 'tahoe @FILENAME' hack (which
was used to run a python file with a PYTHONPATH set to import tahoe's
dependencies).
This adds support for two environments: 'py27' for basic tests, and
'deprecations' to run tests with deprecation warnings turned on (the
latter is meant to be run from a buildbot step that knows how to count
and format the warnings nicely).
Some dependencies are installed in the top-level directory, maybe
because they're required by the build process itself? I'm not sure.
Twisted is one of these, if the system version is not new enough, and
our .gitignore has a clause to ignore the resulting .egg directory. Now
that we've bumped our zope.interface dependency, it sometimes builds a
z.i egg too (even if it doesn't build a Twisted one). So ignore both.
This probably only works on Linux. It uses sudo to mount and unmount the tmpfs,
which may prompt for a password. refs #20
Signed-off-by: David-Sarah Hopwood <david-sarah@jacaranda.org>
