Make python ./setup.py trial output friendlier if there has not been a build. #2272

New Issue

nejucomo · 2014-08-05T17:27:26Z

nejucomo commented

2014-08-05 17:27:26 +00:00

I just did this:

$ python ./setup.py trial
running update_version
git-version: wrote '1.10.0-89-gb7f3585' into 'src/allmydata/_version.py'
running trial
/home/n/virtualenvs/default/bin/python: can't open file 'bin/tahoe': [Errno 2] No such file or directory

Then I asked people in Nuts & Bolts about this and learned some details. It would be potentially helpful for other if the output instead looked like this:

$ python ./setup.py trial
running update_version
git-version: wrote '1.10.0-89-gb7f3585' into 'src/allmydata/_version.py'
running trial
Error: 'bin/tahoe' does not exist. The trial command requires tahoe to be built.

You can explicitly build tahoe by running:

$ python ./setup.py build

You can build and run trial in a single command by running:

$ python ./setup.py test

Note: The usage text already clearifies this:

$ python ./setup.py --help-commands | grep -E 'test|trial'
  test              run unit tests after in-place build
  trial             run trial (use 'bin/tahoe debug trial' for the full set of trial options)

Note: Prior to running trial, I searched in ./docs for something like testing.rst. Zooko tells me this lives on the wiki, but it seems like it should live in ./docs because it's revision specific and useful even when I'm offline.

I just did this: ``` $ python ./setup.py trial running update_version git-version: wrote '1.10.0-89-gb7f3585' into 'src/allmydata/_version.py' running trial /home/n/virtualenvs/default/bin/python: can't open file 'bin/tahoe': [Errno 2] No such file or directory ``` Then I asked people in Nuts & Bolts about this and learned some details. It would be potentially helpful for other if the output instead looked like this: ``` $ python ./setup.py trial running update_version git-version: wrote '1.10.0-89-gb7f3585' into 'src/allmydata/_version.py' running trial Error: 'bin/tahoe' does not exist. The trial command requires tahoe to be built. You can explicitly build tahoe by running: $ python ./setup.py build You can build and run trial in a single command by running: $ python ./setup.py test ``` **Note:** The usage text already clearifies this: ``` $ python ./setup.py --help-commands | grep -E 'test|trial' test run unit tests after in-place build trial run trial (use 'bin/tahoe debug trial' for the full set of trial options) ``` **Note:** Prior to running `trial`, I searched in `./docs` for something like `testing.rst`. Zooko tells me this lives on the wiki, but it seems like it should live in `./docs` because it's revision specific and useful even when I'm offline.

nejucomo added the

labels 2014-08-05 17:27:26 +00:00

nejucomo added this to the undecided milestone 2014-08-05 17:27:26 +00:00

tahoe-lafs added

and removed

labels 2014-08-07 14:14:35 +00:00

tahoe-lafs modified the milestone from undecided to 1.12.0

2014-08-07 14:14:35 +00:00

warner commented

2016-03-22 05:02:25 +00:00

Milestone renamed

warner modified the milestone from 1.12.0 to 1.13.0

2016-03-22 05:02:25 +00:00

warner commented

2016-04-28 07:15:39 +00:00

setup.py trial has been removed. tox is now the recommended way to run tests, and it builds anything that's necessary. So I think this ticket is no longer relevant.

`setup.py trial` has been removed. `tox` is now the recommended way to run tests, and it builds anything that's necessary. So I think this ticket is no longer relevant.

warner added the

invalid

label 2016-04-28 07:15:39 +00:00

warner modified the milestone from 1.13.0 to 1.12.0

2016-04-28 07:15:39 +00:00

warner closed this issue

2016-04-28 07:15:39 +00:00

Sign in to join this conversation.