This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Thomas.Waldmann
Recipients Thomas.Waldmann
Date 2018-07-29.09:03:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532855036.26.0.56676864532.issue34269@psf.upfronthosting.co.za>
In-reply-to
Content
When running the borgbackup tests on 3.7.0, quite some tests will be broken because expected log output is not emitted.

I traced this down up the point when I noticed that reverting the caching feature change of isEnabledFor method in Logger makes the tests work on 3.7.

I reviewed the logging code and the caching change, but could not easily find what is broken. There is of course some suspicion that cache invalidation might be the issue (it is present, but maybe it does not cover all the cases).

See there for more info:
https://github.com/borgbackup/borg/issues/3805

So, I suggest to first revert the caching feature change so we get a fixed logging in 3.7.1 and then to retry to add caching.

Note: I'm at EuroPython sprints today at the borgbackup table.
History
Date User Action Args
2018-07-29 09:03:56Thomas.Waldmannsetrecipients: + Thomas.Waldmann
2018-07-29 09:03:56Thomas.Waldmannsetmessageid: <1532855036.26.0.56676864532.issue34269@psf.upfronthosting.co.za>
2018-07-29 09:03:56Thomas.Waldmannlinkissue34269 messages
2018-07-29 09:03:55Thomas.Waldmanncreate