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
Note: I'm unable to reproduce it locally and only started seeing these errors after upgrading cometbft to v0.37.5 and changing the default db backend from goleveldb to PebbleDB
Addendum - 2025-01-10
This panic is still common in CI and happens ~30% of the time. We use pebbledb everywhere, so the integration tests sometimes fail with "panic: pebbledb: closed" due to some cleanup step happening prematurely in "testutil/testnetwork".
Error Encountered
panic: leveldb: closed
goroutine 903 [running]:
github.com/cometbft/cometbft/store.(*BlockStore).LoadSeenCommit(0xc001b9e240, 0x251eecc?)
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/store/store.go:253 +0x2af
github.com/cometbft/cometbft/consensus.(*State).LoadCommit(0xc001b2d180, 0x3e)
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/consensus/state.go:296 +0x114
github.com/cometbft/cometbft/consensus.(*Reactor).queryMaj23Routine(0xc001454b40, {0x5c3f800, 0xc001a71a00}, 0xc001a71ad0?)
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/consensus/reactor.go:913 +0x1092
created by github.com/cometbft/cometbft/consensus.(*Reactor).AddPeer in goroutine 648
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/consensus/reactor.go:205 +0x37d
FAIL github.com/NibiruChain/nibiru/x/oracle/integration 77.655s
Note from @onikonychev: Using the verbose flag, "-v", in combination with race seems to remove the condition. This still needs more validation from CI runs on main, but the hypothesis seems to be correct based on the changes from #1912
Context
I encountered a strange error in a GitHub action during the integration tests.
Commit: 42a8b65
Note: I'm unable to reproduce it locally and only started seeing these errors after upgrading cometbft to v0.37.5 and changing the default db backend from goleveldb to PebbleDB
Addendum - 2025-01-10
This panic is still common in CI and happens ~30% of the time. We use pebbledb everywhere, so the integration tests sometimes fail with "panic: pebbledb: closed" due to some cleanup step happening prematurely in "testutil/testnetwork".
Error Encountered
panic: leveldb: closed
goroutine 903 [running]:
github.com/cometbft/cometbft/store.(*BlockStore).LoadSeenCommit(0xc001b9e240, 0x251eecc?)
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/store/store.go:253 +0x2af
github.com/cometbft/cometbft/consensus.(*State).LoadCommit(0xc001b2d180, 0x3e)
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/consensus/state.go:296 +0x114
github.com/cometbft/cometbft/consensus.(*Reactor).queryMaj23Routine(0xc001454b40, {0x5c3f800, 0xc001a71a00}, 0xc001a71ad0?)
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/consensus/reactor.go:913 +0x1092
created by github.com/cometbft/cometbft/consensus.(*Reactor).AddPeer in goroutine 648
/home/runner/go/pkg/mod/github.com/cometbft/cometbft@v0.37.5/consensus/reactor.go:205 +0x37d
FAIL github.com/NibiruChain/nibiru/x/oracle/integration 77.655s
Related Tickets
The text was updated successfully, but these errors were encountered: