It's a bug in the test, not the implementation, and so it isn’t user-facing.
However, to my non-Dev eyes that wasn't immediately obvious, so I'm capturing it in an issue so that way if it happens again I'll know not to panic, and maybe at some point the test can be improved.
CI recently had a test failure in lake/journal/journal_test.go. Upon checking with @nwt I was informed:
However, to my non-Dev eyes that wasn't immediately obvious, so I'm capturing it in an issue so that way if it happens again I'll know not to panic, and maybe at some point the test can be improved.
The full stack trace from this recent failure: