| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | tor-rtmock: handle Receiver result inside spawn_join() | Saksham Mittal | 2023-11-21 | 1 | -1/+1 |
| | | |||||
| * | tor-rtmock: change return types to be less concrete | Saksham Mittal | 2023-11-21 | 1 | -1/+1 |
| | | |||||
| * | tor-rtmock: change return type of spawn_join() | Saksham Mittal | 2023-11-21 | 1 | -3/+3 |
| | | | | | | This makes it synchronous. The trait bounds on the return type have also been relaxed to not require Clone | ||||
| * | tor-rtmock: introduce spawn_join() for MockRuntime & MockExecutor | Saksham Mittal | 2023-11-21 | 1 | -0/+13 |
| | | | | | | | | This helps abstract away the need to create a oneshot channel in order to get the return value out of an async function when using MockRuntime. ref: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1727#note_2965352 | ||||
| * | tor-rtmock: MockRuntimeBuilder: new sleep_provider() setter | Ian Jackson | 2023-11-01 | 1 | -1/+10 |
| | | |||||
| * | tor-rtmock: simplify/reorganise MockRuntimeBuilder::build | Ian Jackson | 2023-11-01 | 1 | -4/+3 |
| | | | | | | Always reify a default SimpleMockTimeProvider, and then apply the starting_wallclock to it. This will make the next change fit. | ||||
| * | tor-rtmock: MockRuntime::test_with_various: Print what we're doing | Ian Jackson | 2023-10-16 | 1 | -1/+6 |
| | | | | | | | | | Without this, it can be a bit confusing since you just get the output (if any) of all the test runs, concatenated. It seems sensible to put the framing centrally. And, this would be helpful if the test fails for any reason. | ||||
| * | tor-rtmock: MockRuntime: in advance_*, warn to stderr about looping | Ian Jackson | 2023-10-03 | 1 | -1/+21 |
| | | | | | | This helped me diagnose https://gitlab.torproject.org/tpo/core/arti/-/issues/1040 | ||||
| * | tor-rtmock: Break out advance_inner | Ian Jackson | 2023-10-03 | 1 | -10/+31 |
| | | | | | We're going to want to add something to it. | ||||
| * | tor-rtmock: Abolish deprecated Runtime::advance() | Ian Jackson | 2023-10-03 | 1 | -17/+0 |
| | | | | | | Now we're making breaking changes anyway, in or mock crate, it is a convenient time to get rid of this. | ||||
| * | tor-rtmock: Fix doc refs to advance_* | Ian Jackson | 2023-10-03 | 1 | -2/+2 |
| | | |||||
| * | tor-rtmock: Rename MockRuntime::jump_to to jump_wallclock | Ian Jackson | 2023-10-03 | 1 | -2/+2 |
| | | | | | | | This was named after the method from MockSleepRuntime. The name is confusing because it seems to imply it might do something to the monotonic time. | ||||
| * | tor-rtmock: Abolish just-introduced confusing type alias (fmt) | Ian Jackson | 2023-10-03 | 1 | -1/+1 |
| | | |||||
| * | tor-rtmock: Abolish just-introduced confusing type alias | Ian Jackson | 2023-10-03 | 1 | -8/+8 |
| | | |||||
| * | tor-rtmock: Switch MockRuntime to SimpleMockSleepProvider | Ian Jackson | 2023-10-03 | 1 | -12/+8 |
| | | | | | | | | | | | | | | | | | For now we do this by changing the meaning of the name `MockSleepProvider` in runtime.rs. This is a bodge to reduce noise in this diff. Consequences at call sites: * If the type is named somehow, the other type must be used. * SimpleMockTimeProvider calls it jump_wallclock rather than jump_to, which is IMO a better name. (MockRuntime will change in a moment.) * SimpleMockTimeProvider's advance() function isn't async and doesn't yield. But none of the call sites actually mind that. | ||||
| * | tor-rtmock: Drop some obsolete caveats | Ian Jackson | 2023-10-03 | 1 | -7/+2 |
| | | | | | Nowadays there are methods for this. | ||||
| * | tor-rtmock: MockRuntime: Work around borrowck in Rust 1.65 | Ian Jackson | 2023-09-18 | 1 | -0/+2 |
| | | |||||
| * | tor-rtmock: MockRuntime: Move deprecated advance to end of impl block | Ian Jackson | 2023-09-18 | 1 | -17/+17 |
| | | | | | This will change the ordering in the docs. | ||||
| * | tor-rtmock: MockRuntime: Add tests for advance_* | Ian Jackson | 2023-09-18 | 1 | -0/+177 |
| | | |||||
| * | tor-rtmock: MockRuntime: Provide advance_by() etc. and deprecate .advance() | Ian Jackson | 2023-09-18 | 1 | -1/+100 |
| | | | | | | | | | advance_by can be used in a more natural way, rather than having to manually advance the clock in chunks to avoid triggering only the first sleep. It can also detects some "timeout triggered precisely" edge case bugs. | ||||
| * | tor-rtmock: MockRuntime: Provide spawn_identified() wrapper | Ian Jackson | 2023-09-18 | 1 | -0/+13 |
| | | | | | We should encourage the use of this, rather than Spawn::spawn() | ||||
| * | tor-rtmock: Expose time_until_next_timeout on MockRuntime | Ian Jackson | 2023-08-23 | 1 | -0/+25 |
| | | |||||
| * | tor-rtmock: Use derive-adhoc for composite runtimes | Ian Jackson | 2023-07-07 | 1 | -8/+5 |
| | | |||||
| * | tor-rtmock: Use the same specified field for BlockOn and Spawn | Ian Jackson | 2023-07-06 | 1 | -2/+1 |
| | | | | | These are always the same and probably always will be. | ||||
| * | tor-rtmock: task: clarify progress_until_stalled a little | Ian Jackson | 2023-07-06 | 1 | -0/+2 |
| | | |||||
| * | tor-rtmock: Runtime: Expand on "allowed" documentation | Ian Jackson | 2023-07-06 | 1 | -3/+33 |
| | | |||||
| * | tor-rtmock: MockRuntime: provide test_with_various | Ian Jackson | 2023-07-06 | 1 | -0/+43 |
| | | | | | In both fallible and infallible variants, for convenience. | ||||
| * | tor-rtmock: MockExecutor: Configurable scheduling policy | Ian Jackson | 2023-07-06 | 1 | -1/+13 |
| | | |||||
| * | tor-rtmock: Provide MockRuntime | Ian Jackson | 2023-07-06 | 1 | -0/+129 |
 |
index : mirrors/arti.git | |
| mirror of https://gitlab.torproject.org/tpo/core/arti |
| summaryrefslogtreecommitdiff |