summaryrefslogtreecommitdiff
path: root/crates/tor-rtmock/src
Commit message (Collapse)AuthorAgeFilesLines
* tor-rtmock: get rid of unwrap()Saksham Mittal2023-11-211-1/+1
|
* tor-rtmock: handle Receiver result inside spawn_join()Saksham Mittal2023-11-212-3/+3
|
* tor-rtmock: use expect() insteadSaksham Mittal2023-11-211-1/+2
|
* tor-rtmock: change return types to be less concreteSaksham Mittal2023-11-212-2/+2
|
* tor-rtmock: change return type of spawn_join()Saksham Mittal2023-11-212-6/+6
| | | | | 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 & MockExecutorSaksham Mittal2023-11-212-0/+30
| | | | | | | 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() setterIan Jackson2023-11-011-1/+10
|
* tor-rtmock: simplify/reorganise MockRuntimeBuilder::buildIan Jackson2023-11-011-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 doingIan Jackson2023-10-161-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: MockExecutor: Provide n_tasks accessorIan Jackson2023-10-161-0/+15
|
* oneshot: Apply deferred rustfmt churnIan Jackson2023-10-111-1/+1
| | | | cargo fmt, precisely.
* oneshot: Use veneer in tor-rtmockIan Jackson2023-10-111-1/+1
|
* tor-rtmock: simple_time: Don't export StateIan Jackson2023-10-051-1/+1
| | | | This was a slip.
* tor-rtmock: MockSleepProvider docs: Move example (fmt)Ian Jackson2023-10-051-12/+12
| | | | | Adding "/// " to every line causes rustfmt to have conniptions about the trailing whitespace.
* tor-rtmock: MockSleepProvider docs: Move exampleIan Jackson2023-10-051-0/+73
| | | | | | | | | | | This example demonstrates MockSleepRuntime, which we don't want to use in new tests. It's probably worth keeping it, though, to help with comprehension of existing tests. So move it. This does rather highlight the lack of good overall example/instructions for MockRuntime.
* tor-rtmock: simple_time: Rename `wakers` to `futures` (fmt)Ian Jackson2023-10-051-1/+4
|
* tor-rtmock: simple_time: Rename `wakers` to `futures`Ian Jackson2023-10-051-11/+11
| | | | This is clearer, I think.
* tor-rtmock: simple_time: Rename `pq` to `unready`Ian Jackson2023-10-051-13/+13
| | | | This is clearer, I think.
* tor-rtmock: simple_time: Expand on advance and task orderingIan Jackson2023-10-051-2/+8
|
* tor-rtmock: simple_time: Clarify/correct comments about invariantIan Jackson2023-10-051-2/+2
|
* tor-rtmock: Add deprecation warning to MockSleepRuntimeIan Jackson2023-10-051-1/+7
|
* tor-rtmock: MockSleepProvider docs: Move deprecation discussionIan Jackson2023-10-051-32/+38
| | | | | The module-level docs here are less visible and also not where most of the other stuff was.
* tor-rtmock: MockSleepProvider docs: Compare with SimpleMockTimeProviderIan Jackson2023-10-051-0/+22
|
* tor-rtmock: simple_time: Clarify some things in time_until_next_timeoutIan Jackson2023-10-051-0/+6
|
* tor-rtmock: simple_time: Give formal names to the statesIan Jackson2023-10-051-2/+21
| | | | And introduce a table showing the situations.
* tor-rtmock: simple_time: take() the waker when we wakeIan Jackson2023-10-051-2/+5
| | | | | We don't need it any more; we won't call wake again. So, call .wake() rather than .wake_by_ref().
* tor-rtmock: Provide SimpleTimeProvider: clarify .sleep() innardsIan Jackson2023-10-031-4/+6
| | | | | | Making the SleepFuture first means we don't call .wake_any() with the other invariants violated. This doesn't actually matter with the code as it stands, but it's less confusing this way.
* tor-rtmock: MockRuntime: in advance_*, warn to stderr about loopingIan Jackson2023-10-031-1/+21
| | | | | This helped me diagnose https://gitlab.torproject.org/tpo/core/arti/-/issues/1040
* tor-rtmock: Break out advance_innerIan Jackson2023-10-031-10/+31
| | | | We're going to want to add something to it.
* tor-rtmock: Add a deprecation warning to MockSleepProviderIan Jackson2023-10-031-0/+13
|
* tor-rtmock: Abolish deprecated Runtime::advance()Ian Jackson2023-10-031-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 Jackson2023-10-031-2/+2
|
* tor-rtmock: Rename MockRuntime::jump_to to jump_wallclockIan Jackson2023-10-031-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 Jackson2023-10-031-1/+1
|
* tor-rtmock: Abolish just-introduced confusing type aliasIan Jackson2023-10-031-8/+8
|
* tor-rtmock: Switch MockRuntime to SimpleMockSleepProviderIan Jackson2023-10-032-12/+11
| | | | | | | | | | | | | | | | 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: Provide SimpleTimeProviderIan Jackson2023-10-032-0/+348
|
* tor-rtmock: Drop some obsolete caveatsIan Jackson2023-10-031-7/+2
| | | | Nowadays there are methods for this.
* tor-rtmock: MockRuntime: Work around borrowck in Rust 1.65Ian Jackson2023-09-181-0/+2
|
* tor-rtmock: MockRuntime: Move deprecated advance to end of impl blockIan Jackson2023-09-181-17/+17
| | | | This will change the ordering in the docs.
* tor-rtmock: MockRuntime: Add tests for advance_*Ian Jackson2023-09-181-0/+177
|
* tor-rtmock: MockRuntime: Provide advance_by() etc. and deprecate .advance()Ian Jackson2023-09-181-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() wrapperIan Jackson2023-09-181-0/+13
| | | | We should encourage the use of this, rather than Spawn::spawn()
* tor-rtmock: task backtraces: Expand on spurious backtracesIan Jackson2023-09-131-2/+7
| | | | There's another reason you can see multiple backtraces.
* tor-rtmock: task backtraces: Fix output re backtrace multiplicityIan Jackson2023-09-131-2/+10
| | | | | | | There may be several backtraces for an asleep task. If so, print the prefix for each one. There may be no backtraces for an asleep task. If so, print a message.
* tor-rtmock: task: Add missing doc commentIan Jackson2023-09-131-1/+3
|
* tor-rtmock: task: Add warning about backtrace salienceIan Jackson2023-09-131-2/+34
| | | | With explanation of how it works.
* tor-rtmock: task: Add backtrace dumping callsIan Jackson2023-09-131-4/+4
| | | | | | | Do a full dump, not just a normal Debug dump, when we're panicking in progress_until_stalled. Add a debug dump call to one of the tests, so we can see it working.
* tor-rtmock: task: Add API for printing dumps including backtracesIan Jackson2023-09-131-3/+77
|
* tor-rtmock: task: Capture sleep backtraces, with code to dumpIan Jackson2023-09-131-4/+75
| | | | Currently nothing actually calls the dumping code.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 23:28:48 +0000