|
From: | Michael Tokarev |
Subject: | Re: [PATCH v4 17/32] system/qtest: properly feedback results of clock_[step|set] |
Date: | Mon, 13 Jan 2025 20:52:28 +0300 |
User-agent: | Mozilla Thunderbird |
13.01.2025 19:26, Alex Bennée wrote:
Michael Tokarev <mjt@tls.msk.ru> writes:Ghrm. 46 recipients seems to be quite a bit too aggressive..I think git-publish just accumulates Cc's from each run for a given branch. While I can reset the version counter I'm not sure where I can reset the Cc list from.
I never used git-publish. It's fun to know which other tools do people use :)
08.01.2025 15:10, Alex Bennée wrote:Time will not advance if the system is paused or there are no timer events set for the future. In absence of pending timer events advancing time would make no difference the system state. Attempting to do so would be a bug and the test or device under test would need fixing. Tighten up the result reporting to `FAIL` if time was not advanced.Is this qemu-stable material?Probably not - I guess that was a Cc from a previous series that stuck?
No, it's just that it fixes an issue reported on gitlab (!2687), which apparently weren't fixed in time for 9.2, - that's why :) Thanks, /mjt
[Prev in Thread] | Current Thread | [Next in Thread] |