[OpenSIPS-Users] time going backwards?

[Kingsley Tart]

Hi,

For testing, this code at the top of my route script:

	$var(t0) = $Tsm;
	$var(node_number) = route(get_my_node_number);
	$var(dur) = $Tsm - $var(t0);
	xlog("My node number is $var(node_number) and it took $var(dur) microsecconds to find out\n");

has just logged this:

	Jun 25 20:55:01 [598]: My node number is -1 and it took 65 microsecconds to find out
	Jun 25 20:55:03 [598]: My node number is -1 and it took 67 microsecconds to find out
	Jun 25 20:55:05 [598]: My node number is -1 and it took 64 microsecconds to find out
	Jun 25 20:55:05 [578]: My node number is -1 and it took 602523 microsecconds to find out
	Jun 25 20:55:06 [579]: My node number is -1 and it took -79396 microsecconds to find out
	Jun 25 20:55:07 [598]: My node number is -1 and it took 63 microsecconds to find out
	Jun 25 20:55:07 [580]: My node number is -1 and it took -455503 microsecconds to find out
	Jun 25 20:55:07 [579]: My node number is -1 and it took 108 microsecconds to find out
	Jun 25 20:55:09 [598]: My node number is -1 and it took 78 microsecconds to find out
	Jun 25 20:55:11 [598]: My node number is -1 and it took 68 microsecconds to find out
	Jun 25 20:55:13 [598]: My node number is -1 and it took 66 microsecconds to find out
	Jun 25 20:55:15 [598]: My node number is -1 and it took 68 microsecconds to find out
	Jun 25 20:55:17 [598]: My node number is -1 and it took 65 microsecconds to find out
	Jun 25 20:55:18 [578]: My node number is -1 and it took 107 microsecconds to find out
	Jun 25 20:55:19 [598]: My node number is -1 and it took 71 microsecconds to find out

which is weird because time seems to have gone backwards a couple of times.

Using OpenSIPS 3.1.2 in a VM running Debian 10, with the host being a
CentOS 7 machine running Qemu KVM.

Any idea what's happening here?

Cheers,
Kingsley.