FAIL: TestStoredAnalyzer

[someplaceguy]

Describe the bug

When building gdu on NixOS 24.05, which runs gdu tests, I've observed the following test failure:

--- FAIL: TestStoredAnalyzer (2.12s)
    stored_test.go:64: 
                Error Trace:    /build/source/pkg/analyze/stored_test.go:64
                Error:          Not equal: 
                                expected: 4096
                                actual  : 1024
                Test:           TestStoredAnalyzer

To Reproduce

1. Build gdu on NixOS 24.05

Expected behavior

No test failures.

Screenshots

Building subPackage ./build
Building subPackage ./cmd/gdu
Building subPackage ./cmd/gdu/app
Building subPackage ./internal/common
Building subPackage ./internal/testanalyze
Building subPackage ./internal/testapp
Building subPackage ./internal/testdev
Building subPackage ./internal/testdir
Building subPackage ./pkg/analyze
Building subPackage ./pkg/device
Building subPackage ./pkg/fs
Building subPackage ./pkg/path
Building subPackage ./pkg/remove
Building subPackage ./report
Building subPackage ./stdout
Building subPackage ./tui
buildPhase completed in 1 minutes 54 seconds
Running phase: checkPhase
ok      github.com/dundee/gdu/v5/cmd/gdu/app    0.819s
ok      github.com/dundee/gdu/v5/internal/common        0.204s
&{0xc0002043c0 [] {0 0}} &{0xc0002045f0 [] {0 0}}
--- FAIL: TestStoredAnalyzer (2.12s)
    stored_test.go:64: 
                Error Trace:    /build/source/pkg/analyze/stored_test.go:64
                Error:          Not equal: 
                                expected: 4096
                                actual  : 1024
                Test:           TestStoredAnalyzer
FAIL
FAIL    github.com/dundee/gdu/v5/pkg/analyze    4.894s
FAIL

System (please complete the following information):

• OS: NixOS 24.05
• Version: 5.28.0

Additional context

I suspect that the issue is that disk usage accounting is different in ZFS compared to the filesystems the gdu developer(s) might be using.