Closed Bug 858271 Opened 12 years ago Closed 12 years ago

logLevel property for deviceManager

Categories

(Testing :: Mozbase, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mihneadb, Assigned: mihneadb)

References

Details

Attachments

(1 file)

As mentioned in #793202.
Assignee: nobody → mihneadb
As I was talking to :callek, I'm not sure how we prefer to print the "deprecated" warning. With logger.warn it might not get printed. With a regular print, someone might redirect the logger to a file and just miss the printed warning.
Attachment #733599 - Flags: feedback?(wlachance)
Comment on attachment 733599 [details] [diff] [review] expose the logLevel property; deprecate dm.debug; s/self.logger/self._logger This looks good. I'm honestly not *too* worried about whether or not people see the deprecation warning.
Attachment #733599 - Flags: feedback?(wlachance) → feedback+
(In reply to William Lachance (:wlach) from comment #2) > Comment on attachment 733599 [details] [diff] [review] > expose the logLevel property; deprecate dm.debug; s/self.logger/self._logger > > This looks good. I'm honestly not *too* worried about whether or not people > see the deprecation warning. Specifically because it's not that much of a burden to keep these setters around indefinitely. I'm sure in a few years all our harness code will have been updated for the new setting.
Ok, any need to ask for r? ?
Comment on attachment 733599 [details] [diff] [review] expose the logLevel property; deprecate dm.debug; s/self.logger/self._logger Going ahead and giving this an r+. There were no issues that I could see with the implementation, everything looks good to go.
Attachment #733599 - Flags: review+
Blocks: 793202
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: