transparency-dev / transparency-dev/tessera
armhf: FAIL: TestAntispamFollowerErrorBeforeStream: cannot allocate memory
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 238
- Forks
- 56
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 35
Description
Hi! I help maintain this for Debian. We got the failure below on armhf. Any ideas?
Thanks,
Simon
268s === RUN TestAntispamFollowerErrorBeforeStream
268s badger 2026/07/29 23:00:39 INFO: All 0 tables opened in 0s
268s badger 2026/07/29 23:00:39 INFO: Discard stats nextEmptySlot: 0
268s badger 2026/07/29 23:00:39 INFO: Set nextTxnTs to 0
268s badger 2026/07/29 23:00:39 ERROR: Received err: Error while creating log file in valueLog.open err: while opening file: /tmp/TestAntispamFollowerErrorBeforeStream2101926875/001/000001.vlog err: cannot allocate memory
268s while mmapping /tmp/TestAntispamFollowerErrorBeforeStream2101926875/001/000001.vlog with size: 2147483646. Cleaning up...
268s badger_test.go:217: NewAntispam: failed to open badger: During db.vlog.open err: Error while creating log file in valueLog.open err: while opening file: /tmp/TestAntispamFollowerErrorBeforeStream2101926875/001/000001.vlog err: cannot allocate memory
268s while mmapping /tmp/TestAntispamFollowerErrorBeforeStream2101926875/001/000001.vlog with size: 2147483646
268s --- FAIL: TestAntispamFollowerErrorBeforeStream (0.01s)
268s FAIL
268s FAIL github.com/transparency-dev/tessera/storage/posix/antispam 4.981s
Contributor guide
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 with TestAntispamFollowerErrorBeforeStream and badger_test.go:217, then inspect the Badger setup used by the antispam storage tests. Reproduce the failure from the linked Debian armhf CI run and determine why the test attempts to mmap a 2147483646-byte value log. Done means the test no longer fails from memory allocation on armhf while preserving its intended error-path coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100