[BUG]: IOScheduler yield_util execution semantics are incorrect

[willkill07]

Version

25.02

Which installation method(s) does this occur on?

Source

Describe the bug.

The current test wasn't asserting anything, so I added naive assumptions that resulted in consistent failure.

Looking at the implementation, there is a duration_cast<std::chrono::milliseconds>() which produces information loss and alters the expected behavior.

Minimum reproducible example

TEST_F(TestCoroIoScheduler, YieldUntil)
{
    auto scheduler = coroutines::IoScheduler::get_instance();

    coroutines::clock_t::time_point target_time{};

    auto task = [scheduler, &target_time]() -> coroutines::Task<> {
        target_time = coroutines::clock_t::now() + 10ms;
        co_await scheduler->yield_until(target_time);
    };
    
    coroutines::sync_wait(task());

    auto current_time = coroutines::clock_t::now();

    ASSERT_GE(current_time, target_time);
}

Relevant log output

Full env printout

Other/Misc.

No response

Code of Conduct

• I agree to follow MRC's Code of Conduct
• I have searched the open bugs and have found no duplicates for this bug report