How do I make stem log info-level to test/data/tor_log?

I ran the stem tests with --log info, but that just makes stem log info-level errors to the terminal. It doesn't change test/data/tor_log.

changed milestone to %Tor: 0.4.1.x-final

Trac:
Parent Ticket: #30591 (moved)

added actualpoints::0.1 component::archived/stem milestone::Tor: 0.4.1.x-final owner::atagar parent::30591 points::0.1 priority::medium resolution::implemented severity::normal sponsor::31-can status::closed tor-ci-fail-sometimes type::defect labels

Hi teor. The log level of tor_log is not presently configurable...

https://gitweb.torproject.org/stem.git/tree/test/runner.py#n72

I'd be happy to go in several directions with this. What is your preference?

• Change the default log runlevel to info.
• Provide a config option or environment variable to customize the runlevel.
• Provide a config option to add arbitrary torrc lines (this way you could add 'Log info /my/path' or customize the test torrc in any way you'd like).

Replying to atagar:

• Provide a config option or environment variable to customize the runlevel.

Let's provide a way to customise the log level in the file.

If we ever need arbitrary torrc lines, we can do that change later.

Replying to atagar:

• Provide a config option to add arbitrary torrc lines (this way you could add 'Log info /my/path' or customize the test torrc in any way you'd like).

I just talked with nickm on IRC. We want to capture all the controller messages from tor.

So that means we'd like "Log [control]debug /path/to/file", or any other arbitrary torrc line.

Does stem have a way to log all it's control messages?

Hi teor. Chewing on this a bit I decided to make two changes...

1. Stem now empties its tor data directory between runs
2. Integ test tor logging is now at the debug runlevel

If you disagree with either of these changes or this doesn't do the trick for ya then just let me know.

Does stem have a way to log all it's control messages?

Yup. As mentioned on irc trace runlevel logging provide request/reply logs for its control port. That is to say, exactly what we send and receive...

% ./run_tests.py --integ --log TRACE
05/27/2019 16:02:23 [TRACE] Sent to tor: PROTOCOLINFO 1
05/27/2019 16:02:23 [TRACE] Received from tor:
  250-PROTOCOLINFO 1
  250-AUTH METHODS=NULL
  250-VERSION Tor="0.4.1.0-alpha-dev"
  250 OK
05/27/2019 16:02:23 [TRACE] Sent to tor: AUTHENTICATE
05/27/2019 16:02:23 [TRACE] Received from tor: 250 OK
05/27/2019 16:02:23 [TRACE] Sent to tor: SETEVENTS STATUS_SERVER SIGNAL CONF_CHANGED
05/27/2019 16:02:23 [TRACE] Received from tor: 250 OK
... etc...

Feel free to reopen if you need anything else.

Trac:
Resolution: N/A to implemented
Status: new to closed

Trac:
Actualpoints: N/A to 0.1
Points: N/A to 0.1

Setting as sponsor 31 can, because we use these jobs to make sure our refactoring works.

Trac:
Sponsor: N/A to Sponsor31-can

closed

changed time estimate to 48m

added 48m of time spent

mentioned in issue #30591 (moved)