GNU testsuite comparison:

GNU test failed: tests/misc/tee. tests/misc/tee is passing on 'main'. Maybe you have to rebase?
Skip an intermittent issue tests/misc/stdbuf (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/timeout/timeout (fails in this run but passes in the 'main' branch)

GNU testsuite comparison:

Skip an intermittent issue tests/misc/tee (fails in this run but passes in the 'main' branch)

Testing this has the same problem as #7796. The test would need to be run with elevated privileges and change the EUID and EGID of the process to be different from the actual UID and GID.
See: #7796 (comment)

how can i test this locally ? :)

See the Reproduce section in the related issue #7812. The main branch prints the wrong output while this branch should print the expected output.

GNU testsuite comparison:

Skip an intermittent issue tests/misc/tee (fails in this run but passes in the 'main' branch)
Skipping an intermittent issue tests/timeout/timeout (passes in this run but fails in the 'main' branch)

GNU testsuite comparison:

Skip an intermittent issue tests/timeout/timeout (fails in this run but passes in the 'main' branch)

GNU testsuite comparison:

Skip an intermittent issue tests/misc/tee (fails in this run but passes in the 'main' branch)
Skipping an intermittent issue tests/misc/stdbuf (passes in this run but fails in the 'main' branch)

The test_id_pretty_print_suid_binary test can be run by enabling the chmod and chown features. To test the output with different EUID and EGID values than the real UID and GID, you can use the following command:

sudo true && cargo test --features id,chown,chmod test_id_pretty_print_suid_binary

The sudo true command enables running commands with sudo without a password within the test, assuming the sudo's timestamp_timeout is not configured to 0 (always prompt for a password).

GNU testsuite comparison:

Skipping an intermittent issue tests/misc/tee (passes in this run but fails in the 'main' branch)