[go: up one dir, main page]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

After setting a future time for WSL, the flow of time slowed down #12082

Closed
1 of 2 tasks
DengYuncheng27 opened this issue Sep 26, 2024 · 2 comments
Closed
1 of 2 tasks

After setting a future time for WSL, the flow of time slowed down #12082

DengYuncheng27 opened this issue Sep 26, 2024 · 2 comments
Labels
needs-author-feedback

Comments

@DengYuncheng27
Copy link

Windows Version

Microsoft Windows [version 10.0.19045.4894]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Linux version 5.15.133.1-microsoft-standard-WSL2 (root@1c602f52c2e4) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Oct 5 21:02:42 UTC 2023

Distro Version

Release: 20.04

Other Software

No response

Repro Steps

  1. I disabled time synchronization and stopped the NTP service.
bubble@WINDOWS-7AJJBFF:~$ timedatectl set-ntp false
bubble@WINDOWS-7AJJBFF:~$ timedatectl status
               Local time: Fri 2024-09-27 00:28:44 CST
           Universal time: Thu 2024-09-26 16:28:44 UTC
                 RTC time: Thu 2024-09-26 08:18:01
                Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
  1. Set a future time:
bubble@WINDOWS-7AJJBFF:~$ sudo date -s "2024-9-27 12:00:00"
Fri Sep 27 12:00:00 CST 2024
  1. Observe the difference between its time flow and the standard time flow.
  2. Observe the results. For example, I set the time one hour ahead. At this moment, the time difference is 1 hour. After 1 minute, the difference becomes 59 minutes and 55 seconds, with an error of a few seconds. After one hour, this error will grow to a few minutes.

Expected Behavior

The flow of time should be consistent. After I set a future time, no matter how much time passes, the time difference between them should remain constant.

Actual Behavior

After I set a future time, the flow of time on the WSL machine slows down.

Diagnostic Logs

No response
@github-actions GitHub Actions
Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@microsoft-github-policy-service Microsoft GitHub Policy Service
Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-author-feedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DengYuncheng27