SimulateBackend AdjustTime is not adjusting time at all, or either in unexpected ways.

[bonedaddy]

While using SimulateBackend I attempted to roll forward the time of the simulated blockchain using AdjustTime(604800 *time.Second) which should roll forward time by a week. Checking the returned error value shows that it is nil, however from all my testing it appears that time does not actually roll forward, and local system time is used. Attempting to call functions which should work after time is rolled forward, do not work.

go version: go1.10.11 linux/amd64

Using the lates go-ethereum version.

[dimchansky]

I had the similar issue, until I've added Commit after AdjustTime. Before making transaction in the distant future, adjust time and commit, and only then make transactions, like:

	if err := backend.AdjustTime(72 * time.Hour); err != nil {
		panic(err)
	}
	backend.Commit()

	// now make transactions "after 72 hours"

[ligi]

Attempting to call functions which should work after time is rolled forward, do not work.

which functions do you mean here?

[holiman]

Yes, you need to Commit to make the pending state 'live'. However, we should

• forbid adjusting time if txs are already added to pending block,
• OR, make sure to apply the time change before we re-add the txs

[karalabe]

I myself would forbid time adjustments on non-empty blocks. The fix should be trivial, but let's also add a test to repro.

[bonedaddy]

@ligi I meant smart contract functions that require block timestamps to be past a certain point.