cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14059) Root logging formatter broken in dtests
Date Tue, 05 Dec 2017 01:17:00 GMT


Jeff Jirsa commented on CASSANDRA-14059:


> Root logging formatter broken in dtests
> ---------------------------------------
>                 Key: CASSANDRA-14059
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Joel Knighton
>            Assignee: Joel Knighton
>            Priority: Minor
> Since the ccm dependency in dtest was bumped to {{3.1.0}} in {{7cc06a086f89ed76499837558ff263d84337acba}},
when dtests are run with --nologcapture, errors of the following form are printed:
> {code}
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/logging/", line 861, in emit
>     msg = self.format(record)
>   File "/usr/lib64/python2.7/logging/", line 734, in format
>     return fmt.format(record)
>   File "/usr/lib64/python2.7/logging/", line 469, in format
>     s = self._fmt % record.__dict__
> KeyError: 'current_test'
> Logged from file, line 485
> {code}
> This is because CCM no longer installs a basic root logger configuration, which is probably
a more correct behavior than what it did prior to this change. Now, dtest installs its own
basic root logger configuration which writes to 'dtest.log' using the formatter {{'%(asctime)s,%(msecs)d
%(name)s %(current_test)s %(levelname)s %(message)s'}}. This means that anything logging a
message must provide the current_test key in its extras map. The dtest {{debug}} and {{warning}}
functions do this, but logging from dependencies doesn't, producing these {{KeyError}} s.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message