You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Aptly's test suite on linux-arm64 or darwin-arm64, a segmentation fault is hit during the ImportChangesFiles test. The trace goes back through goleveldb into snappy. This appears to be related to golang/snappy#62, the suggested fix is to update to snappy 0.0.4 or higher. goleveldb updated to this version of snappy in v1.0.1-0.20210819022825-2ae1ddf74ef7 (syndtr/goleveldb#365).
Possible Implementation
Fixed by updating goleveldb:
aptly % go get github.com/syndtr/goleveldb/[email protected]
go: upgraded github.com/syndtr/goleveldb v1.0.1-0.20190923125748-758128399b1d => v1.0.1-0.20210819022825-2ae1ddf74ef7
aptly % go test ./deb/ -check.f 'ImportChangesFiles'
ok github.com/aptly-dev/aptly/deb 0.227s
Your Environment
darwin-arm64 on an M1 Mac (where else?) and linux-amd64 via Podman Machine on the same host (it's running Fedora Core OS in a VM)
Full output
Output of "go test -v ./deb/ -gocheck.v=true -check.f 'ImportChangesFiles'"
Since aptly is running a modified and locally maintained version of goleveldb, as to be found in /database/goleveldb/ inherited from the original maintainer, I think we would need to backport the goleveldb patch you mentioned to try to fix the test error you encountered.
In the long run, we should discover whether we can use upstream goleveldb, and patch it to what we need it to be, or better yet, try to make aptly only use what is provided upstream anyways. (I said it on this bug tracker, and I'll do so again: I am not a Go developer, but I can read source files and I know a thing or two about software development in general.)
Maybe someone familiar with goleveldb can give us hints on how to progress with getting rid of our local goleveldb package?
Detailed Description
When running Aptly's test suite on linux-arm64 or darwin-arm64, a segmentation fault is hit during the ImportChangesFiles test. The trace goes back through goleveldb into snappy. This appears to be related to golang/snappy#62, the suggested fix is to update to snappy 0.0.4 or higher. goleveldb updated to this version of snappy in
v1.0.1-0.20210819022825-2ae1ddf74ef7
(syndtr/goleveldb#365).Possible Implementation
Fixed by updating goleveldb:
Your Environment
darwin-arm64 on an M1 Mac (where else?) and linux-amd64 via Podman Machine on the same host (it's running Fedora Core OS in a VM)
Full output
Output of "go test -v ./deb/ -gocheck.v=true -check.f 'ImportChangesFiles'"
The text was updated successfully, but these errors were encountered: