Summary: | sys-apps/flashrom-1.3.0-r1 fails tests (MUSL-SYSTEM): 1 cmocka test flashrom FAIL 0.04s (exit status 255 or signal 127 SIGinvalid) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Marek Szuba <marecki> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | grobian, matoro_gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 906737 | ||
Attachments: |
build.log
1-testlog.txt |
Description
Agostino Sarubbo
2023-06-15 13:06:17 UTC
Created attachment 863862 [details]
build.log
build log and emerge --info
Created attachment 863863 [details]
1-testlog.txt
1-testlog.txt
Error(s) that match a know pattern in addition to what has been reported in the summary: Run-time dependency libjaylink found: NO (tried pkgconfig and cmake) [ LINE ] --- ../flashrom-v1.3.0/tests/lifecycle.c:46: error: Failure! The failing test is: [ RUN ] linux_mtd_probe_lifecycle_test_success Testing flashrom_programmer_init for programmer=linux_mtd ... __wrap_stat is called __wrap_fopen is called __wrap_fread is called __wrap_fclose is called __wrap_stat is called __wrap_fopen is called __wrap_fread is called __wrap_fclose is called [ FAILED ] linux_mtd_probe_lifecycle_test_success It fails because it tries to open /sys/class/mtd, which I also don't have on my system (Linux 6.1.27-gentoo-r1). I don't see it on glibc either (as well as musl). So I believe this is actually a "generic" (non-musl) bug, where the test should be disabled, for it can only work on hosts that have mtd (storage) enabled in the kernel. (In reply to Fabian Groffen from comment #4) > So I believe this is actually a "generic" (non-musl) bug, where the test > should be disabled, for it can only work on hosts that have mtd (storage) > enabled in the kernel. That is not quite correct - while it is true that the programmer linux_mtd tries to open files in /sys/class/mtd, the test suite mocks them. Which would imply that it is not flashrom but dev-util/cmocka that MUSL breaks. I see a very similar error even on glibc, just the right-hand side is 0x2 instead of 0x1. stderr: [ PASSED ] 7 test(s). [ PASSED ] 1 test(s). [ PASSED ] 10 test(s). [ ERROR ] --- 0 != 0x2 [ LINE ] --- ../flashrom-v1.3.0/tests/lifecycle.c:25: error: Failure! |