[PATCH] fixup! test: Add pytest suite for NVMEM framework
Ahmad Fatoum
a.fatoum at pengutronix.de
Tue Jun 24 01:59:24 PDT 2025
Hi,
On 6/24/25 10:30, Oleksij Rempel wrote:
> On Tue, Jun 24, 2025 at 10:17:12AM +0200, Ahmad Fatoum wrote:
>> If CONFIG_DEBUG_PROBES is enabled, barebox will print an info log
>> whenever a device is probed. This breaks one test case in the newly
>> introduced nvmem tests, because running the nvmem command results in two
>> lines instead of one:
>>
>> probe-> rmem1
>> rmem1
>>
>> A better solution might be disabling stderr, but for now, let's just
>> have the test check all lines that appeared after running the command.
>>
>> This fixes CI breakage in next.
>>
>> Cc: Oleksij Rempel <o.rempel at pengutronix.de>
>> Signed-off-by: Ahmad Fatoum <a.fatoum at pengutronix.de>
>
> LGTM
>
> May be better to keep it as separate patch, not as fixup? Since It provides
> important information.
Fine with me either way. If Sascha prefers a separate patch I would
suggest as commit message title:
test: nvmem: fix test failure with CONFIG_DEBUG_PROBES
Cheers,
Ahmad
>
> Best Regards,
> Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list