Software /
code /
prosody
Annotate
plugins/mod_unknown.lua @ 13027:012d6e7b723a
integration tests: Preserve unmocked time.monotonic()
With monotonic() frozen, timers may fail to trigger. This caused problems
after the new util.startup changes that moved the server-started event to a
timer. The timer wouldn't trigger, the event didn't fire, and prosody would
fail to daemonize.
All the tests that depend on specific time behaviour are depending on wall
clock time, so only mocking util.time.now() and os.time() fixes those.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 06 Apr 2023 14:00:54 +0100 |
parent | 6003:28a90f5fea46 |
rev | line source |
---|---|
6003
28a90f5fea46
modulemanager: Always load a platform-specific module, add stub modules for Windows and unknown platforms
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
1 -- Unknown platform stub |
28a90f5fea46
modulemanager: Always load a platform-specific module, add stub modules for Windows and unknown platforms
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
2 module:set_global(); |
28a90f5fea46
modulemanager: Always load a platform-specific module, add stub modules for Windows and unknown platforms
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
3 |
28a90f5fea46
modulemanager: Always load a platform-specific module, add stub modules for Windows and unknown platforms
Kim Alvefur <zash@zash.se>
parents:
diff
changeset
|
4 -- TODO Do things that make sense if we don't know about the platform |