chainguard-dev / chainguard-dev/tw
syspeek test in melange.yaml fails on aarch64
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 36
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 6
Description
Attempts to land the tw.yaml changes into melange https://github.com/wolfi-dev/os/pull/63749 and https://github.com/wolfi-dev/os/pull/63618 were unsuccessful.
That was ultimately because aarch64 test failed in syspeek section.
the first reason for that failure is parsing of architecture.
objdump -f /usr/bin/crane
/home/build # objdump -f /usr/bin/crane
/usr/bin/crane: file format elf64-littleaarch64
architecture: aarch64, flags 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x000000000008b850
parsing that with the current code ends up with empty ARCH which then fails with non-obvious error.
I'd like to see syspeek updated somehow to have better error checking and error messages so that it is more obvious what went wrong.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the aarch64 failure in the syspeek test from melange.yaml, using the shown objdump output as the parsing input. Trace how the architecture value is parsed and how an empty ARCH produces the current error. Done means the failure reports the parsing problem clearly and the aarch64 syspeek test handles the architecture correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100