test_chcon::valid_reference_repeated_reference fails on `kind: InvalidInput, message: "Invalid argument"`

---- test_chcon::valid_reference_repeated_reference stdout ----
touch: /tmp/.tmpzMbKk5/a.tmp
set_file_context: 'guest_u:object_r:etc_t:s0:c42' => '/tmp/.tmpzMbKk5/a.tmp'.
touch: /tmp/.tmpzMbKk5/wrong.tmp
set_file_context failed: 'guest_u:object_r:etc_t:s42:c0' => '/tmp/.tmpzMbKk5/wrong.tmp': lsetfilecon() failed on path '/tmp/.tmpzMbKk5/wrong.tmp'.
thread 'test_chcon::valid_reference_repeated_reference' panicked at tests/by-util/test_chcon.rs:539:64:
called `Result::unwrap()` on an `Err` value: IO1Path { source: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }, operation: "lsetfilecon()", path: "/tmp/.tmpzMbKk5/wrong.tmp" }
---- test_dd::test_seek_past_dev stdout ----
run: sudo -E --non-interactive whoami
thread 'test_dd::test_seek_past_dev' panicked at tests/common/util.rs:2940:55:
called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }

Start with tests/by-util/test_chcon.rs around line 539 and tests/common/util.rs around line 2940, then run the reported tests to reproduce both failures. Check whether the failures depend on the environment shown in the output, including SELinux file contexts and the unavailable sudo command; done means the tests pass or their prerequisites are handled explicitly.