> Should we wait for Ravi to implement this, or can we go ahead and do it
> ourselves as needed?
Feel free, Ravi will be busy with other controller functionality for
quite a while.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torpr
(Sorry, wasn't subscribed to tor-dev@, so these last couple of messages
didn't go there...)
On 6/29/12 4:09 PM, Damian Johnson wrote:
I think the question here is that it seems like one should be able to get
all the descriptors from the running Tor process via
GETINFO desc/all-recent
> Keep in mind that metrics tarballs can be huge. stem's tests probably
> shouldn't download one or more of these tarballs in an automatic integ
> test run.
Oops yup. Should have mentioned that. We're just picking out a
descriptor that seems to exercise most of the parsing. This is just
for a san
2012/6/28 Damian Johnson :
>> Erik and I have finished the proc.py integration tests
>
> Great! I'm looking forward to checking them out.
>
>> Tomorrow, we will be starting the next Stem task regarding the Tor Export
>> project. Do you have any recommendations on where we should start exploring
>
On 6/28/12 11:37 PM, Damian Johnson wrote:
> - integ tests are pretty short, and just run the parser against some
> test data from the metrics archive and the cached consensus
Keep in mind that metrics tarballs can be huge. stem's tests probably
shouldn't download one or more of these tarballs
> Erik and I have finished the proc.py integration tests
Great! I'm looking forward to checking them out.
> Tomorrow, we will be starting the next Stem task regarding the Tor Export
> project. Do you have any recommendations on where we should start exploring
> in the Stem documentation?
Hmm,
