On Wed, 25 Mar 2026 at 13:58, Bruce Ashfield via
lists.openembedded.org
<[email protected]> wrote:
> For something like this to be considered for merging, I'd have expected
> a lot more information.
>
> Is the test coverage the same as before ?
> What are the results of the tests versus the previous harness ?
> Is it truly a drop in replacement for the previous runner ?
> .. etc
>
> Switching the executable is the easy part, ensuring that it actually works
> a replacement is the hard part.

>> Assisted-by: Claude, Anthropic

I have to add that this line ^^^ doesn't inspire confidence in the
patch either. On the contrary, it raises suspicions that the code was
written quickly after the issue was raised yesterday in the tech
meeting, and wasn't actually tested well or at all. The commit message
*must* reassure that it was.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#233907): 
https://lists.openembedded.org/g/openembedded-core/message/233907
Mute This Topic: https://lists.openembedded.org/mt/118498904/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to