libelektra: Rust test case fails on master
https://build.libelektra.org/jenkins/blue/organizations/jenkins/libelektra/detail/master/18/pipeline reports:
test kdb::test::can_use_kdb ... FAILED
failures:
---- kdb::test::can_use_kdb stdout ----
thread 'kdb::test::can_use_kdb' panicked at 'internal error: entered unreachable code', elektra/src/kdb.rs:318:17
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
failures:
kdb::test::can_use_kdb
test result: FAILED. 32 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out
error: test failed, to rerun pass '-p elektra --lib'
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (17 by maintainers)
This was an error I introduced in this PR and I thought it was related to this issue. But it’s actually unrelated, so unfortunately this issue is not fixed.
Maybe there is no key in the backend of the used parentKey, then it also returns 0 as there is no change to the keyset.
Looks like
test_rust_elektrafailed in PR #3126.It’s a different error this time unrelated to the error mapping. A
Permanent(Logical(Internal(...)))error occurred, but it wasn’t printed out. So that’s all the information that I have. I’ll added a small fix to master for printing that as well, that’s all I can do unfortunately. Next time we can see the error if the same one happens again.Some error code was given that wasn’t known to the mapper. The mapping for Installation (“C01200”) errors was missing and I added that in #3047.
But that doesn’t really explain why there occurred an error in the first place. The test case isn’t raising an error. And the latest PR #3038 you merged didn’t even touch the rust bindings. I’ll try to figure it out in the PR above.