We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running an embedded inproc stored node, being used in a test pointed at /tmp, and with RUST_LOG set to trace, I get the following output:
ERROR my_project > Error ... TRACE mio::poll > deregistering event source from poller TRACE want > signal: Closed TRACE mio::poll > deregistering event source from poller TRACE want > signal: Closed TRACE mio::poll > deregistering event source from poller TRACE want > signal: Closed TRACE mio::poll > deregistering event source from poller TRACE want > signal: Closed TRACE mio::poll > deregistering event source from poller TRACE sled::pagecache::iobuf > skipping roll_iobuf due to empty segment TRACE sled::pagecache::iobuf > bumping atomic header lsn to -1 TRACE sled::pagecache::iobuf > skipping roll_iobuf due to empty segment TRACE sled::pagecache::iobuf > skipping roll_iobuf due to empty segment TRACE sled::pagecache::iobuf > skipping roll_iobuf due to empty segment TRACE sled::pagecache::iobuf > skipping roll_iobuf due to empty segment TRACE sled::pagecache::iobuf > skipping roll_iobuf due to empty segment TRACE sled::pagecache::iobuf > skipping roll_iobuf due to empty segment ^C
This also causes failing tests in CI to churn endlessly.
Using: sled: 0.34.7 rustc: 1.63.0 OS: arch (btw)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When running an embedded inproc stored node, being used in a test pointed at /tmp, and with RUST_LOG set to trace, I get the following output:
This also causes failing tests in CI to churn endlessly.
Using:
sled: 0.34.7
rustc: 1.63.0
OS: arch (btw)
The text was updated successfully, but these errors were encountered: