also looking at this
fix: honor discovery-mode CLI options
#17
10 files
+192
-24
Review threads live on the whole diff, not on one commit, so none are shown here - a thread's line means something in the branch's final form, and painting it into an intermediate step would put it on code it is not about.
| @@ -403,14 +403,12 @@ test "TimeoutContext extension" { | ||
| 403 | 403 | // Extend timeout |
| 404 | 404 | try context.extend(100); |
| 405 | 405 | |
| 406 | compat.sleep(120 * std.time.ns_per_ms); | |
| 407 | ||
| 408 | // Should not be timed out (extended to 200ms total) | |
| 406 | // Move the clock origin instead of relying on scheduler timing. Under a | |
| 407 | // loaded CI runner, a nominal 120ms sleep can exceed the 200ms deadline. | |
| 408 | context.start_time = compat.milliTimestamp() - 120; | |
| 409 | 409 | try std.testing.expect(!context.isTimedOut()); |
| 410 | 410 | |
| 411 | compat.sleep(100 * std.time.ns_per_ms); | |
| 412 | ||
| 413 | // Should be timed out now | |
| 411 | context.start_time = compat.milliTimestamp() - 220; | |
| 414 | 412 | try std.testing.expect(context.isTimedOut()); |
| 415 | 413 | } |
| 416 | 414 | |