-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-88352: Fix logging.TimedRotatingFileHandler #116191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-88352: Fix logging.TimedRotatingFileHandler #116191
Conversation
serhiy-storchaka
commented
Mar 1, 2024
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- 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.
- Issue: TimedRotatingFileHandler overwrite log #88352
* 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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
…-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 <[email protected]>
|
* 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.