github-actions[bot]
commented
1 month ago 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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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 scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) 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:
- WSL Clock still not updating correctly - frequently out of sync (#9183), similarity score: 0.80
- Clock skew detected during build (#8318), similarity score: 0.79
- WSL2 - clock problems during build (#4975), similarity score: 0.79
- system date is not same with windows (WSL 2) (#6974), similarity score: 0.79
- WSL2 clock becomes unsynced on Desktop system (#7255), similarity score: 0.78
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
surfacepatterns
Windows Version
Microsoft Windows [Version 10.0.22631.3737]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
CBL-Mariner 2.0.20240628
Other Software
No response
Repro Steps
wslinstance.Expected Behavior
I expect to observe clock skew quite rarely, and to have it impact my work on a much less frequent basis.
Actual Behavior
Here are a couple examples.
dmesgoutputPartial (relevant) output when
mesontests fail, which are run as part of building binary RPMs:(In the build log this excerpt is from, there were 32 such clock skew failures. I've tried building this package five times today, and each instance results in a similar amount of failures.)
Note that I've seen the issues about clock skew after sleeping. A few things make me think this is different:
sudo hwclock -sdoesn't seem to change anything.Diagnostic Logs
No response