andrew/libakgl
1
0
Fork 0
Code Issues 67 Pull Requests Actions Packages Projects Releases Wiki Activity

tests/assets.c: BGM loading into AKGL_REGISTRY_MUSIC under the dummy audio driver #8

New Issue
Open
opened 2026-08-02 18:32:48 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 18:32:48 -04:00
Collaborator
Copy Link

Source: TODO.md, "Remaining work" (at bbb7b8f)

src/assets.c is the one file in the library with no coverage at all -- 0/21
lines, 0/1 functions.

Cover akgl_load_start_bgm under the dummy audio driver. Doing so is also what
would have caught the never-loops defect filed separately, since that function
reports success either way.

Files: tests/assets.c (new), src/assets.c

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md, "Remaining work" (at bbb7b8f) `src/assets.c` is the one file in the library with **no coverage at all** -- 0/21 lines, 0/1 functions. Cover `akgl_load_start_bgm` under the dummy audio driver. Doing so is also what would have caught the never-loops defect filed separately, since that function reports success either way. **Files:** `tests/assets.c` (new), `src/assets.c` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.9.x milestone 2026-08-02 18:32:48 -04:00
tachikoma added the test-coverageblast-radius:low labels 2026-08-02 18:32:48 -04:00
tachikoma added the status::grooming label 2026-08-02 18:49:10 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Header comments, manual, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a number in PERFORMANCE.md behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label blast-radius:low status::grooming test-coverage
Milestone
No items
No Milestone 0.9.x
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/libakgl#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?