supplied instant is later than self

[JesseAbram]

Having an issue running statemine and a relay chain with polkadot launch.

The polkadot launch config file is here https://github.com/JesseAbram/asset_cli_tool/blob/master/config.json

The branches were
cumulus branch :02bf5acf6c101b1bd890c25490ec88f5350d22e0
polkadot branch : 88db2d85587f26f007cc66c111157126d0466ecc

Polkadot launch will run and complete then panic after about 2 min.
The panic error is here
https://pastebin.com/vtLv322M

The machine it is ran on has
4 cores, 16gb ram and plenty of free hd space

Note this was not on my hardware and I was unable to reproduce this issue. I have also found references to this issue.
paritytech/substrate#4949

cargo clean did not work and on the machine this was used on it happens consistently.

[nuke-web3]

Hey @JesseAbram - should this issue live on the https://github.com/paritytech/polkadot-launch/issues ?
happy to transfer the issue if so. I can also attempt to reproduce locally if you think it's worthwhile.

[JesseAbram]

No def not a polkadot launch thing, I would expect it is in the polkadot repo itself, but because we are launching polkadot statemine and substrate, I am not sure which repo this would be in

[JesseAbram]

Issue resolved, the issue was in rust and due to the clock used. This is a good issue to check out to help understand rust-lang/rust#86470. The clock used by the VM was kvm-clock and was mitigated by changing the clock

[JesseAbram]

Just for some extra details the clock was changed to acpi_pm and this article was referenced on how to do that https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_real_time/7/html/reference_guide/chap-timestamping

As well this is not always OS or Kernel related as with a VM the clock used can be related to the hypervisor