Major Description
This test fails with a dubious indication that delivery arrived before a predicted delivery time.
There is some uncertainty with respect to the test timing declarations based on event.reactor.schedule calls with integer timing granularity and the connection statistics gathered with Node queries, also with integer timing granularity.
If the connection takes only a few hundred microseconds to start up then the router's internal uptime and last delivery times may appear to be a full second behind the test times. The router uptime may be 1.999900 S and the external test expects >= 2.000000 S and so the test fails. This is normal for systems where the times are rounded down to the nearest whole second.
The fix for this test is to relax the timing limits by one second.
Normal Test
| conn/iter | self.uptime | self.lastDlv | conn uptime | conn lastDlv |
|---|---|---|---|---|
| send/1 | 5 | None | 5 | None |
| recv/1 | 5 | None | 5 | None |
| send/1 | 7 | 2 | 7 | 2 |
| recv/1 | 7 | 2 | 7 | 2 |
Failing Test
| conn/iter | self.uptime | self.lastDlv | conn uptime | conn lastDlv |
|---|---|---|---|---|
| send/1 | 5 | None | 6 | None |
| recv/1 | 5 | None | 6 | None |
| send/1 | 7 | 2 | 7 | 1 |
| recv/1 | 7 | 2 | 7 | 1 |
Attachments
Issue Links
- links to