gh-88352: Fix logging.TimedRotatingFileHandler#116191
gh-88352: Fix logging.TimedRotatingFileHandler#116191serhiy-storchaka merged 1 commit intopython:mainfrom
Conversation
* Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change.
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
* Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change. (cherry picked from commit fee86fd) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
GH-116208 is a backport of this pull request to the 3.12 branch. |
* Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change. (cherry picked from commit fee86fd) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
GH-116209 is a backport of this pull request to the 3.11 branch. |
|
…-116208) * Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change. (cherry picked from commit fee86fd) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
…-116209) * Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change. (cherry picked from commit fee86fd) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
|
* Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change.
|
This just failed under WASI: https://buildbot.python.org/all/#/builders/1046/builds/4510/steps/7/logs/stdio . Maybe a flaky test? |
|
Yes, a flaky test. It can fail even on Linux if increase the CPU load. |
|
I am puzzled. The failure is not actually depended on the CPU load. It is random, with probability about one or few percents. An obvious way to fix it (increasing the time delta for |
|
It should be fixed by #116409. |
* Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change.
* Do not overwrite already rolled over files. It happened at midnight or during the DST change and caused the loss of data. * computeRollover() now always return the timestamp larger than the specified time. * Fix computation of the rollover time during the DST change.
Uh oh!
There was an error while loading. Please reload this page.