setClock from node-litesvm does not work according to Solana program

[AuroraLantean]

I am using the latest @coral-xyz/anchor ^0.31.1.
When I set my deadline as a future time in my TS test file:

        const clock = svm.getClock();
	clock.unixTimestamp = BigInt(deadline);
	svm.setClock(clock);
	svm.warpToSlot(1000n);

and when I ran above code in my Anchor test with my Solana program below:

let clock = Clock::get()?;
let time = clock.unix_timestamp as u32;
msg!("Solana time:{:?}", time); // time from Solana program

The time from my Solana program still shows my current unix time!! Why??

Reference to your Clock test:

• https://www.anchor-lang.com/docs/testing/litesvm#time-travel
• https://github.com/LiteSVM/litesvm/blob/master/crates/node-litesvm/tests/clock.test.ts

[nonergodic]

Fwiw, I seem to be running into the same problem (and calling expireBlockhash() didn't help either).

[Aursen]

Are you using node-litesvm or the anchor wrapper?

[nonergodic]

node-litesvm. I rebuilt the .node file (litesvm.linux-x64-gnu.node in my case) from the repo because the npmjs package is quite outdated and caused issues.

[Aursen]

Do you have a snippet of code to reproduce the issue?

[nonergodic]

... false alarm on my part. 🤦‍♂️ Took a closer at my code and the tests in the repo and realized that I was trying to advance the time via this.liteSvm.getClock().unixTimestamp = ... instead of calling setClock().

Total PEBCAK, sorry for wasting your time.