Mikeal Rogers [:mikeal] (mrogers@) Assignee
	Description • 17 years ago

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3pre) Gecko/2008012804 Minefield/3.0b3pre
Build Identifier: 

The talos utils module does a bunch of output masking and timestamping that could all be replaced using the standard python logging module and would make it more efficient/standardized.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

	Mikeal Rogers [:mikeal] (mrogers@) Assignee
	Comment 1 • 17 years ago

Patch to replace utils output functionality with python logging module.

	alice nodelman [:alice] [:anode]
	Comment 5 • 17 years ago

Comment on attachment 301326 [details] [diff] [review]
Logging patch 4

     ffprocess.Sleep()
     #set up the counters for this test
     cm = CounterManager("firefox", counters)
+    cm.setDaemon(1)
     cm.startMonitor()
     counter_results = {}

setDaemon breaks talos on windows machines, raises an AttributeError.

	Mikeal Rogers [:mikeal] (mrogers@) Assignee
	Comment 6 • 17 years ago

Fixing windows failure.

Sets better spacing minimums on log output for better alignment.

	alice nodelman [:alice] [:anode]
	Comment 7 • 17 years ago

Comment on attachment 301608 [details] [diff] [review]
Logging patch 5

Raised the following error after a run of tsvg (with --debug --noisy).

Traceback (most recent call last):
  File "c:\Python25\lib\logging\__init__.py", line 744, in emit
    msg = self.format(record)
  File "c:\Python25\lib\logging\__init__.py", line 630, in format
    return fmt.format(record)
  File "c:\Python25\lib\logging\__init__.py", line 418, in format
    record.message = record.getMessage()
  File "c:\Python25\lib\logging\__init__.py", line 288, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting

This didn't crash anything but I'd rather it not show up with any frequency in the logs.

	Mikeal Rogers [:mikeal] (mrogers@) Assignee
	Comment 8 • 17 years ago

This is currently on the back burner.

	Mikeal Rogers [:mikeal] (mrogers@) Assignee
	Comment 9 • 16 years ago

Alice, do we plan on taking this at any time?

Since any change, regardless of how minor, seem to screw the numbers a bit is this worth the risk?

If not we should just resolve as invalid.

	alice nodelman [:alice] [:anode]
	Comment 10 • 16 years ago

This is blocked on comment #7.  I'm not worried about hurting the numbers, more that we don't currently have a patch posted here that works cleanly.

	Mikeal Rogers [:mikeal] (mrogers@) Assignee
	Comment 11 • 16 years ago

Wow, a whole lot has changed since that last patch was generated.

Not only does the patch fail to apply in any way, but my local copy of these changes couldn't be brought up to date via cvs up.

At this point, this would have to be completely re-written from scratch and all we would really get out of it is a slightly different logging format than we have now.

	alice nodelman [:alice] [:anode]
	Comment 12 • 16 years ago

Sounds like this is at an impasse.  I'm going to mark wontfix since we do currently have a logging strategy that works - even if it doesn't happen to be the most pretty solution.

We can re-open if a patch becomes workable.