Mercurial > prosody-hg
annotate spec/util_time_spec.lua @ 13491:cf367ab36fcc
util.prosodyctl: Use notify socket to wait for Prosody to be ready
Previously, prosodyctl only waits for the pidfile to appear, which does
not necessarily mean that Prosody is fully ready to receive traffic.
By waiting until Prosody says it's ready via the systemd notify socket
we know for sure that Prosody is really ready.
Notably this should ensure that when running `make integration-test`
Prosody is really ready when Scansion starts running tests.
Not sure if this timeout handling is optimal.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 19 May 2024 13:06:55 +0200 |
| parents | aba99b6539f5 |
| children |
| rev | line source |
|---|---|
| 9193 | 1 describe("util.time", function () |
| 2 local time; | |
| 3 setup(function () | |
| 4 time = require "util.time"; | |
| 5 end); | |
| 6 describe("now()", function () | |
| 7 it("exists", function () | |
| 8 assert.is_function(time.now); | |
| 9 end); | |
| 10 it("returns a number", function () | |
| 11 assert.is_number(time.now()); | |
| 12 end); | |
| 13 end); | |
| 14 describe("monotonic()", function () | |
| 15 it("exists", function () | |
| 16 assert.is_function(time.monotonic); | |
| 17 end); | |
| 18 it("returns a number", function () | |
| 19 assert.is_number(time.monotonic()); | |
| 20 end); | |
| 21 it("time goes in one direction", function () | |
| 22 local a = time.monotonic(); | |
| 23 local b = time.monotonic(); | |
| 24 assert.truthy(a <= b); | |
| 25 end); | |
| 26 end); | |
| 27 end); | |
| 28 | |
| 29 | |
| 30 | |
| 31 |