New issue
Advanced search Search tips

Issue 643590 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Sep 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Top-level `logging.basicConfig` call in benchmark_runner.py

Reported by gurr...@yandex-team.ru, Sep 2 2016 
While the comment there about preventing other modules from setting their own logging during import is true, I actually didn't find any other modules that do this, and doing this also prevents other modules that import benchmark_runner from setting their own logging with `logging.basicConfig`.
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 5 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/038fe389148a6cde4132742671814dc1b7785b44

commit 038fe389148a6cde4132742671814dc1b7785b44
Author: catapult-deps-roller <catapult-deps-roller@chromium.org>
Date: Mon Sep 05 10:20:08 2016

Roll src/third_party/catapult/ 1f08948ad..0c42939b6 (1 commit).

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/1f08948ad3a9..0c42939b6f14

$ git log 1f08948ad..0c42939b6 --date=short --no-merges --format='%ad %ae %s'
2016-09-05 gurrrik Fix use of logging, set logging level for wpr server

BUG= 643590 

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2310843002
Cr-Commit-Position: refs/heads/master@{#416521}

[modify] https://crrev.com/038fe389148a6cde4132742671814dc1b7785b44/DEPS
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 5 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment