Test failure in `test_has_write_permission` module.
Hello. This issue is related to #200.
I am trying to package felix for Void Linux. The packages are built and tested in a chroot environment and I suspect this might be the cause.
Build log: https://github.com/void-linux/void-packages/actions/runs/11123962654/job/30908516803?pr=52442
test state::tests::test_has_write_permission ... FAILED
test state::tests::bench_update_parallel ... ok
test functions::tests::bench_format_txt_bwrap1 ... ok
test functions::tests::bench_format_txt1 ... ok
failures:
---- state::tests::test_has_write_permission stdout ----
thread 'state::tests::test_has_write_permission' panicked at src/state.rs:2059:9:
assertion failed: !has_write_permission(p.as_path()).unwrap()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
state::tests::test_has_write_permission
test result: FAILED. 31 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.20s
Hm. What is the rustc version on your environment?
Hm. What is the rustc version on your environment?
$ rustc --version
rustc 1.81.0 (eeb90cda1 2024-09-04) (Void Linux)
The packages are built and tested in a chroot environment and I suspect this might be the cause.
Maybe you're right. In other Linux environment this test is passed. Is it fatal that you cannot pass all tests?
It’s part of our build pipeline. I can disable the internal test suite, but I would definitely prefer a fix for the tests themselves so that they work in chroot as well.
Fixed via https://github.com/kyoheiu/felix/pull/300 . Could you try building?
Closed via https://github.com/kyoheiu/felix/pull/300