tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

say that 'python setup.py trial' is only for backward compatibility 

[Imported from Trac: page AdvancedInstall, version 65]
daira 2013-08-31 15:07:11 +00:00
parent 8ccb8bd234
commit 1a561e536c
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
AdvancedInstall.md

@ -240,14 +240,15 @@ There are a few other supported ways to run tests:
* `bin/tahoe debug trial`. This will *not* rebuild (if a build was needed, * `bin/tahoe debug trial`. This will *not* rebuild (if a build was needed,
> some tests may fail). It accepts all of the same options as Twisted's `trial` > some tests may fail). It accepts all of the same options as Twisted's `trial`
> script; use `bin/tahoe debug trial --help` to see help for these. > script; use `bin/tahoe debug trial --help` to see help for these.
* `python setup.py trial` does the same thing as `bin/tahoe debug trial`,
> although it doesn't support all of the `trial` options (and the test suite
> must be specified using `-s`). It's supported mainly for backward
> compatibility.
* `make test` does the same thing as `python setup.py test`. * `make test` does the same thing as `python setup.py test`.
* `make quicktest` does the same thing as `bin/tahoe debug trial`. * `make quicktest` does the same thing as `bin/tahoe debug trial`.
Running `trial` directly is not supported because it will not necessarily The following way of running tests is supported only for backward compatibility:
* `python setup.py trial` does almost the same thing as `bin/tahoe debug trial`,
> but doesn't support all of the `trial` options, and the test suite must be
> specified using `-s`).
Running `trial` directly is *not* supported, because it will not necessarily
put the correct libraries (the same ones that would be used by `bin/tahoe`) put the correct libraries (the same ones that would be used by `bin/tahoe`)
on Python's `sys.path`. on Python's `sys.path`.