mirrors/arti.git/crates/tor-rtmock/src/runtime.rs, branch arti-v1.1.11 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11 2023-11-21T15:59:38Z tor-rtmock: handle Receiver result inside spawn_join() 2023-11-21T15:59:38Z Saksham Mittal git@gotlou.com 2023-11-21T15:59:38Z urn:sha1:804b66127008d194f5691602219812f6e982df1d tor-rtmock: change return types to be less concrete 2023-11-21T12:37:11Z Saksham Mittal git@gotlou.com 2023-11-21T12:37:11Z urn:sha1:f1bb16f55f0534aef9c7040912d731f97dc9c59e tor-rtmock: change return type of spawn_join() 2023-11-21T06:16:21Z Saksham Mittal git@gotlou.com 2023-11-21T06:07:01Z urn:sha1:f3204c99787f748d6fc9d0123929f8dd1adc3e4f 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 2023-11-21T06:16:20Z Saksham Mittal git@gotlou.com 2023-11-17T11:43:31Z urn:sha1:63f9ccbd73745eb6dd506f9fae29968edd34e868 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 2023-11-01T13:19:45Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-31T17:23:31Z urn:sha1:ee96e5e454ba5db27daaab0f8757732994454f0b tor-rtmock: simplify/reorganise MockRuntimeBuilder::build 2023-11-01T13:19:45Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-31T10:58:28Z urn:sha1:111300f54fb03b8b2b4269466abf5a8038338a94 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 2023-10-16T12:38:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-12T13:28:37Z urn:sha1:6345e398fb81e93b5f1f6618a8c83f5821f610af 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 2023-10-03T15:35:14Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-03T15:01:30Z urn:sha1:bfd3936ba5c5e0bc26c419356a108e5ec565702d This helped me diagnose https://gitlab.torproject.org/tpo/core/arti/-/issues/1040 tor-rtmock: Break out advance_inner 2023-10-03T15:35:14Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-03T14:50:13Z urn:sha1:886d4d0a221a3bbb0e78eb5e75b95c678a694085 We're going to want to add something to it. tor-rtmock: Abolish deprecated Runtime::advance() 2023-10-03T15:35:14Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-03T13:58:01Z urn:sha1:a63e0d188114470bc6bf5e75fa5bc2c5ab9ea732 Now we're making breaking changes anyway, in or mock crate, it is a convenient time to get rid of this.