>> You want to point at your tor binary, I think, not just the path
>> (i.e. something like "--tor ../tor-2.3.*/src/or/tor")
>
> That did the trick, thanks:
Oops, I'm sorry about not being clearer about that.
> Why do the tests take so long to run? I noticed that most of the time
> almost no CPU
On Thu, Dec 20, 2012 at 12:31 PM, wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> You want to point at your tor binary, I think, not just the path
> (i.e. something like "--tor ../tor-2.3.*/src/or/tor")
That did the trick, thanks:
$ time ./run_tests.py --integ --tor ../tor-0.2.3.25
> It looks like the data directory was created as expected:
>
> $ find test/data/
> test/data/
> test/data/log
> test/data/torrc
>
> Unfortunately ./run_tests.py --help isn't telling me about e.g. a
> verbosity level option to help give more of a clue as to what is going
> wrong :-(
>
> Any more id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You want to point at your tor binary, I think, not just the path
(i.e. something like "--tor ../tor-2.3.*/src/or/tor")
If you're liking Python, I'd also love some feedback on txtorcon's API
(it has 98% unit-test coverage, but doesn't depend on a runn
On Thu, Dec 20, 2012 at 11:48 AM, Damian Johnson wrote:
>> Is that a bug that it says 'TESTING PASSED' even though it failed to
>> start Tor? Is the permission denied error because I need to be root to
>> run the tests? If so, how to change the tests so that being root isn't
>> necessary?
>
> Yea,
> Is that a bug that it says 'TESTING PASSED' even though it failed to
> start Tor? Is the permission denied error because I need to be root to
> run the tests? If so, how to change the tests so that being root isn't
> necessary?
Yea, saying 'PASSED' rather than 'FAILED' would be a bug.
No, the t
On Wed, Dec 19, 2012 at 8:57 PM, Simon wrote:
> On Wed, Dec 19, 2012 at 4:35 PM, Nick Mathewson wrote:
>> What's your favorite C mocking solution for integrating with existing
>> codebases without much disruption?
>
> This could be worth a separate thread. I'm not aware of really good
> solutions
On Thu, Dec 20, 2012 at 10:50 AM, Damian Johnson wrote:
>> So I have a built and make tested tor-0.2.3.25/ folder and stem/ in a
>> parallel folder. When I run the command then I get the following:
>>
>> $ ./run_tests.py --integ
>> Unable to start tor, 'tor' does not exists.
>>
>> How can I run th
> So I have a built and make tested tor-0.2.3.25/ folder and stem/ in a
> parallel folder. When I run the command then I get the following:
>
> $ ./run_tests.py --integ
> Unable to start tor, 'tor' does not exists.
>
> How can I run the tests on the Tor built in the tor-0.2.3.25/ folder?
Just run
On Wed, Dec 19, 2012 at 6:31 PM, Damian Johnson wrote:
>> [...]
>>> Maybe there is no automated testing for any Tor projects? At least a
>>> quick search on the wiki only found [1] which lists possible ways to
>>> test (but was created 7 months ago and apparently not updated since
>>> and collect
10 matches
Mail list logo
