| /external/slf4j/slf4j-api/src/main/java/org/slf4j/helpers/ |
| D | SubstituteLoggerFactory.java | 43 …final ConcurrentMap<String, SubstituteLogger> loggers = new ConcurrentHashMap<String, SubstituteLo… field in SubstituteLoggerFactory
46 SubstituteLogger logger = loggers.get(name); in getLogger()
49 SubstituteLogger oldLogger = loggers.putIfAbsent(name, logger); in getLogger()
57 return new ArrayList<String>(loggers.keySet()); in getLoggerNames()
61 return new ArrayList<SubstituteLogger>(loggers.values()); in getLoggers()
65 loggers.clear(); in clear()
|
| /external/autotest/server/cros/power/ |
| D | power_telemetry_logger.py | 102 loggers = self._load_and_trim_data(start_ts, end_ts)
105 self._upload_data(loggers, checkpoint_logger)
294 def _upload_data(self, loggers, checkpoint_logger): argument
301 for logger in loggers:
365 loggers = list()
386 loggers.append(logger)
388 return loggers
|
| /external/autotest/client/site_tests/power_Dummy/ |
| D | control | 17 loggers, and measurement dashboards. Run for a short amount of time, collect
19 Loggers included in this test are all loggers in power_test and
|
| /external/slf4j/slf4j-api/src/main/java/org/slf4j/ |
| D | LoggerFactory.java | 177 List<SubstituteLogger> loggers = TEMP_FACTORY.getLoggers(); in fixSubstitutedLoggers() local
179 if (loggers.isEmpty()) { in fixSubstitutedLoggers()
188 for (SubstituteLogger subLogger : loggers) { in fixSubstitutedLoggers()
|
| /external/python/cpython2/Doc/library/ |
| D | logging.config.rst | 93 :param disable_existing_loggers: If specified as ``False``, loggers which
98 disable any existing loggers unless they or
104 existing loggers were *always* disabled.
236 * *loggers* - the corresponding value will be a dict in which each key
252 The specified loggers will be configured according to the level,
268 * *disable_existing_loggers* - whether any existing loggers are to be
285 the object graph of loggers, handlers, filters, formatters at
286 run-time, once a configuration is set up; the verbosity of loggers and
288 loggers, propagation flags). Changing the object graph arbitrarily in
297 ``propagate`` settings in the ``loggers`` and ``root`` entries.
[all …]
|
| D | logging.rst | 45 * Handlers send the log records (created by loggers) to the appropriate
64 Loggers that are further down in the hierarchical list are children of loggers
66 loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` are all
68 package hierarchy, and identical to it if you organise your loggers on a
79 handlers of higher level (ancestor) loggers, in addition to any handlers
81 loggers' handlers - neither the level nor filters of the ancestor loggers in
85 of ancestor loggers.
93 hierarchy, then it will see all events logged by all descendant loggers,
107 NOTSET, its chain of ancestor loggers is traversed until either an ancestor with
518 initialized with 'A.B' will allow events logged by loggers 'A.B', 'A.B.C',
[all …]
|
| /external/python/cpython3/Doc/library/ |
| D | logging.config.rst | 105 :param disable_existing_loggers: If specified as ``False``, loggers which
110 disable any existing non-root loggers unless
174 disable existing loggers, you will need to use a JSON format for
279 * *loggers* - the corresponding value will be a dict in which each key
295 The specified loggers will be configured according to the level,
311 * *disable_existing_loggers* - whether any existing non-root loggers are
328 the object graph of loggers, handlers, filters, formatters at
329 run-time, once a configuration is set up; the verbosity of loggers and
331 loggers, propagation flags). Changing the object graph arbitrarily in
340 ``propagate`` settings in the ``loggers`` and ``root`` entries.
[all …]
|
| D | logging.rst | 41 * Handlers send the log records (created by loggers) to the appropriate
60 Loggers that are further down in the hierarchical list are children of loggers
62 loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` are all
64 package hierarchy, and identical to it if you organise your loggers on a
75 passed to the handlers of higher level (ancestor) loggers, in addition to
77 ancestor loggers' handlers - neither the level nor filters of the ancestor
78 loggers in question are considered.
81 of ancestor loggers.
89 hierarchy, then it will see all events logged by all descendant loggers,
107 NOTSET, its chain of ancestor loggers is traversed until either an ancestor with
[all …]
|
| /external/python/cpython2/Doc/howto/ |
| D | logging.rst | 331 of components: loggers, handlers, filters, and formatters.
334 * Handlers send the log records (created by loggers) to the appropriate
340 Log event information is passed between loggers, handlers, filters and
344 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
346 separators. For example, a logger named 'scan' is the parent of loggers
350 A good convention to use when naming loggers is to use a module-level logger,
358 The root of the hierarchy of loggers is called the root logger. That's the
390 The flow of log event information in loggers and handlers is illustrated in the
450 down in the hierarchical list are children of loggers higher up in the list.
451 For example, given a logger with a name of ``foo``, loggers with names of
[all …]
|
| D | logging-cookbook.rst | 232 # Now, define a couple of other loggers which might represent areas in your
343 # Now, define a couple of other loggers which might represent areas in your
745 'loggers': {
|
| /external/python/cpython3/Doc/howto/ |
| D | logging.rst | 343 of components: loggers, handlers, filters, and formatters.
346 * Handlers send the log records (created by loggers) to the appropriate
352 Log event information is passed between loggers, handlers, filters and
356 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
358 separators. For example, a logger named 'scan' is the parent of loggers
362 A good convention to use when naming loggers is to use a module-level logger,
370 The root of the hierarchy of loggers is called the root logger. That's the
404 The flow of log event information in loggers and handlers is illustrated in the
464 down in the hierarchical list are children of loggers higher up in the list.
465 For example, given a logger with a name of ``foo``, loggers with names of
[all …]
|
| D | logging-cookbook.rst | 236 # Now, define a couple of other loggers which might represent areas in your
347 :class:`QueueHandler` to those loggers which are accessed from
354 attach only ``QueueHandlers`` to your loggers) for the benefit of other
426 # Now, define a couple of other loggers which might represent areas in your
878 loggers = ['foo', 'foo.bar', 'foo.bar.baz',
882 logger = logging.getLogger(random.choice(loggers))
920 'loggers': {
946 This variant shows how you can e.g. apply configuration for particular loggers
1205 before any loggers that you care about are instantiated.
1217 developers can set a suitable filter on their loggers, but they would have to
[all …]
|
| /external/python/cpython2/Lib/logging/ |
| D | config.py | 523 loggers = config.get('loggers', EMPTY_DICT)
524 for name in loggers:
526 self.configure_logger(name, loggers[name], True)
609 loggers = config.get('loggers', EMPTY_DICT)
610 for name in loggers:
624 self.configure_logger(name, loggers[name])
|
| /external/python/cpython3/Lib/logging/ |
| D | config.py | 518 loggers = config.get('loggers', EMPTY_DICT)
519 for name in loggers:
521 self.configure_logger(name, loggers[name], True)
603 loggers = config.get('loggers', EMPTY_DICT)
604 for name in loggers:
616 self.configure_logger(name, loggers[name])
|
| /external/testng/src/main/java/org/testng/log4testng/ |
| D | Logger.java | 121 private static final Map<Class, Logger> loggers = Maps.newHashMap(); field in Logger
148 Logger logger= loggers.get(pClass); in getLogger()
154 loggers.put(pClass, logger); in getLogger()
478 loggers.clear(); in testInitialize()
|
| /external/libphonenumber/demo/war/WEB-INF/ |
| D | logging.properties | 12 # Set the default logging level for all loggers to WARNING
|
| /external/slf4j/slf4j-migrator/ |
| D | LIMITATIONS.txt | 13 - if a method declares multiple loggers on the same line, the conversion will not be complete. Exam…
|
| /external/slf4j/slf4j-simple/src/test/resources/ |
| D | simplelogger.properties | 2 # Simple implementation of Logger that sends all enabled log messages, for all defined loggers, to …
|
| /external/autotest/server/ |
| D | server_job.py | 1012 loggers, _, _ = select.select(self.warning_loggers, [], [], 0)
1014 for logger in loggers:
1031 if not loggers:
|
| /external/grpc-grpc/summerofcode/2018/ |
| D | naresh.md | 182 where the module level loggers don't initialize a default logging handler.
|
| /external/google-breakpad/src/common/mac/ |
| D | GTMLogger.m | 94 // as a writer. Our inner loggers should apply no formatting since the main
|
| /external/python/cpython2/Misc/NEWS.d/ |
| D | 2.7b1.rst | 370 sort the existing loggers.
|
| D | 2.6b1.rst | 307 fileConfig()'s disabling of old loggers is now conditional via an optional
|
| /external/python/google-api-python-client/ |
| D | CHANGELOG | 227 - Use named loggers instead of the root logger. (#206)
|
| /external/python/cpython3/Doc/whatsnew/ |
| D | 2.7.rst | 468 The following example configures two loggers, the root logger and a
496 # Specify all the subordinate loggers
497 'loggers': {
|