Open 030 opened 5 years ago
Bump, any workarounds for this?
what about -rtc base=localtime,clock=host
?
I solved this issue leaving open in the snapshot of the VM a batch script that every 30 seconds will sync the time. The solution while a bit overkill it works with not performance impact for the test or the host.
I have problem when run tests in parallel execution, some tests are run on the same container. I've fixed problem with time sync using @emilorol update, but problem with multiple tests running on the same container is still there. Do you have some solution for me ? Is it possible to sync time through entrypoint.sh ? Also I've tried with -rtc base=localtime,clock=host and it doesn't help.
@nilic10 try the solution I mention with a batch script that runs every 30 second to keep the clock in sync. I know it is not the more awesome but it does work very good. The only down side is that you might have to re-save your image to add it.
@emilorol I mentioned that I've tried with your update with batch script runs on every 2 seconds, but I've still have problem.
Hi is there any update on this?. or work around available? even I am facing same issue with tests running with same session id.
@nilic10 try the solution I mention with a batch script that runs every 30 second to keep the clock in sync. I know it is not the more awesome but it does work very good. The only down side is that you might have to re-save your image to add it.
Could you please provide a script to synchronize the time?
I am facing the problem that if the time difference is more than 15 hours, then my script refuses to synchronize the time.
My script:
w32tm /resync /force
One could add instructions for configuring NTP